telegram-ads-mcp
Related Servers
Alternatives to telegram-ads-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to create, edit, and manage Telegram Ads campaigns by preparing structured ad packages, uploading media, committing changes, and reading account statistics through a Chrome extension bridge.2-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage and analyze Google Ads campaigns through tools for listing campaigns, retrieving settings, performance metrics, ad groups, and running custom GAQL queries.2 npmMIT
- AlicenseAqualityBmaintenanceAn MCP server that lets AI agents read and manage Telegram Ads campaigns, including listing accounts and ads, reading stats and budgets, and creating/updating ads, CPM, status, and budget by driving the real ads.telegram.org web UI through Playwright with a reused cookie-based login session.111MIT
- FlicenseAqualityBmaintenanceEnables AI agents to manage Google Ads campaigns (Search and UAC) through natural language, with read tools always available and guarded write operations for budgets, campaigns, ad groups, and keywords.3-
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to manage Google Ads accounts by providing tools for querying account data and performing write operations such as updating campaign budgets, statuses, and bidding strategies.2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to read, send, and organize Telegram messages and chats. Supports tools for listing chats, fetching messages, sending/reply, archiving, muting, and folder management.1MIT
TDQS
Scored across 25 tools
Most tools clearly target a distinct resource or action, and the get/create/edit/delete/launch/clone ad family is well-separated. A few pairs could confuse agents, notably check_session vs. get_account (both return account/session state) and create_ad vs. launch_ad vs. send_target_to_review (atomic vs. composite paths), though descriptions reduce ambiguity.
Tool names overwhelmingly follow a consistent verb_noun pattern (get_ads, create_ad, edit_ad, delete_ad, clone_ad, upload_media). The manage_audience/manage_event/manage_funds umbrella names are predictable, and minor variants like log_out or check_ad_post do not disrupt the overall convention.
At 25 tools, this sits at the heavy end of the 16–25 borderline range. The broad Telegram Ads domain justifies much of the surface, but some session/account tools and wrapper workflows could be consolidated into fewer, higher-level tools.
The surface comprehensively covers auth and session management, account switching, the full ad lifecycle (create, read, update, delete, clone, launch, review, stats), media upload, targeting, audiences, events, and funds. There are no obvious dead ends for the stated domain.