Coverage & limitations
The official hosted implementation covers all 45 canonical Telegram Ads methods, including the deprecated editAdStatus alias to editAd. See the complete method, native-parameter and permission mapping. Native request/response schemas remain strict and preserve provider field names. The nine convenience read tools remain available when the root is granted.
| Area | Implemented | Permission / limits |
|---|---|---|
| Accounts | Root and related discovery, account information, create/edit | Exact concrete rows; newly created accounts are never automatically granted. |
| Ads | Lists/details, create/edit, start/pause, review, deletion | Advertising rights; create requires both management groups. Funded ads can spend on resume. |
| Money | Balances, transactions, account/ad allocation and withdrawal, CPM/daily limits | Budget rights; root-related transfers require both endpoints and explicit settlement polling. |
| Statistics and reports | Native account/ad statistics and official monthly report | End exclusive, at most 1000 daily/five-minute intervals. |
| Media | Staged ad photo/video and website photo, then native multipart | JPEG/PNG 5 MiB / MP4 20 MiB / website JPEG/PNG 1 MiB. No URLs/paths/base64. |
| Audiences and Pixel | Lists/details and create/edit/delete, audience membership and Pixel events | Advertising rights for changes; up to 10000 provider-format phone hashes per input list. |
| Targeting | Languages/topics/countries, locations and channel/bot lookup | Numeric peer IDs must previously have been resolved by that account through username. |
| Provider preview, recommendations and query validation | Unavailable through the official runtime | No HTML, cookie or browser fallback; no moderation approval claim. |
Read-only is required for each selected account; Manage advertising and Manage budgets are independent additions. A scope union cannot widen another account's rights. Every mutation uses a durable, stable operation ID and explicit recovery; unknown writes are never automatically replayed. Media geometry, video duration, balances and current account restrictions remain provider validations. Unexpected provider responses become PROTOCOL_DRIFT; raw provider error text is not exposed.
All 45 methods have synthetic typed schema and actual MCP dispatch coverage, including exact grants, money combinations, upload streaming, failures, revocation and operation recovery. Ordinary live checks remain read-only. This implementation coverage does not establish real provider write success, a deployed version, live monitoring delivery or production availability. Concrete live provider mutations require explicit test authorization. tgads.tlmtr.dev is the development endpoint.