telegram-ads-mcp

Overview Schema Source Related Servers Discussions Admin

edit_ad

Modify existing Telegram ads by updating only the fields you provide—text, media, budget, schedule, or status—to avoid recreating ads.

Instructions

Edit an ad. Only provided fields are sent.

picture=True shows the avatar, picture=False turns it off (sends picture=0).
clear_media=True removes attached photo/video.
budget_action + budget_amount changes total budget (increase resumes a depleted Stopped ad).
Targeting cannot be changed after creation — clone_ad instead.
confirm: required to activate or change budget unless TG_ADS_WRITE_GATE=open.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`cpm`	No
`text`	No
`ad_id`	Yes
`media`	No
`title`	No
`active`	No
`button`	No
`confirm`	No
`picture`	No
`schedule`	No
`audience_id`	No
`clear_media`	No
`promote_url`	No
`schedule_tz`	No
`daily_budget`	No
`website_name`	No
`activate_date`	No
`budget_action`	No
`budget_amount`	No
`views_per_user`	No
`deactivate_date`	No
`conversion_event`	No
`schedule_tz_custom`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 30, 2026

addedInput schema / properties / confirm

Added value: +{
+  "default": false,
+  "title": "Confirm",
+  "type": "boolean"
+}

First observedv0.2.0Aug 29, 2026

TDQS

A4.1/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description reveals critical behaviors beyond the annotations: only provided fields are sent, picture=True/False toggles the avatar, clear_media removes media, budget_action/budget_amount changes total budget and can resume a depleted Stopped ad, and confirm gates activation/budget changes. This is rich, actionable behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loads the most important invariant ('Only provided fields are sent'), then packs targeted details into short scannable lines. Every sentence provides useful information without filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema, the tool is a complex 23-parameter mutation with no schema-level parameter documentation. The description covers the riskiest behaviors and the confirm requirement, but it leaves many fields with unclear formats, prerequisites, or interactions, making it incomplete for reliable invocation in all cases.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 23 parameters and 0% schema description coverage, the description must carry the semantic burden, but it only explains a handful: picture, clear_media, budget_action, budget_amount, and confirm. Most remaining parameters (text, title, schedule, audience_id, daily_budget, conversion_event, etc.) are left to inference from their names alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Edit an ad,' a specific verb and resource that distinguishes it from sibling tools like create_ad, delete_ad, and clone_ad. The added context about only provided fields being sent reinforces that this is a partial-update operation, not a full replacement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit guidance for a key distinction: targeting cannot be changed after creation, and clone_ad should be used instead. It also implies edit_ad is for updating existing ads rather than creating or deleting them. However, it does not provide a broader when-to-use comparison against other siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.