telegram-ads-mcp

Overview Schema Source Related Servers Discussions Admin

manage_event

Create, list, rename, and delete conversion events and pixels in Telegram Ads. Controls conversion tracking by managing event setups and pixels with confirmation for irreversible deletions.

Instructions

Conversion events and pixels. action=list|create|rename|delete|create_pixel.

list is not gated. delete is danger + two-step confirm_hash.
Access denied → code:access_denied, hint:skip (do not retry).

Input Schema

TableJSON Schema

Name	Required	Default
`title`	No
`action`	Yes
`confirm`	No
`event_id`	No
`event_type`	No	custom
`confirm_hash`	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

C2.7/5.0

Behavior1/5

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

The description discloses useful behavioral traits like delete danger and the access-denied skip hint, but it directly contradicts the annotation destructiveHint=false by calling delete dangerous. Because the description and annotations conflict, behavioral transparency must be scored as 1.

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

Conciseness4/5

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

The description is compact, scannable, and front-loads the action list and safety notes. The opening noun phrase is slightly awkward, but every sentence contributes operational value and no space is wasted.

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?

Even though an output schema exists, the description is not complete enough to call the tool reliably across all five actions. It does not specify parameter requirements for create, rename, or create_pixel, and the roles of confirm, event_id, event_type, and title remain unclear.

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?

Schema description coverage is 0%, so the description must compensate for parameter meaning. It only clarifies action and confirm_hash; it does not explain event_id, event_type, title, or confirm, nor does it map required parameters per action. This is only partial compensation for a six-parameter tool.

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

Purpose4/5

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

The description names the resource (conversion events and pixels) and enumerates all supported operations via action=list|create|rename|delete|create_pixel. This is specific enough to distinguish it from sibling tools like manage_audience or manage_funds, though it is phrased as a noun fragment rather than an explicit verb statement.

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

Usage Guidelines3/5

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

It gives action-specific guidance: list is not gated, delete is dangerous and needs a two-step confirm_hash, and access-denied results should not be retried. However, it does not explain when to choose this tool over sibling tools or which action to prefer for a given scenario, leaving selection somewhat implied.

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