AdsMCP

Overview Schema Source Related Servers Discussions Admin

ads_telegram_ads_api_create_ad

Create a Telegram Ads advertisement via the official API. Requires confirmation and defaults to paused with zero initial budget for safe setup.

Instructions

Create one Telegram Ads advertisement through the official API. This is a provider write; confirm=true is required. Defaults to paused with zero initial budget.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "promote_url": "<promote_url>",
      "cpm": "<cpm>",
      "placement": "<placement>",
      "target": "<target>",
      "confirm": "<confirm>"
    },
    "name": "ads_telegram_ads_api_create_ad"
  }
}

Input Schema

Name	Required	Description	Default
`cpm`	Yes
`text`	No
`title`	Yes
`target`	Yes
`confirm`	Yes
`is_paused`	No
`placement`	Yes
`account_id`	No
`timeout_ms`	No
`promote_url`	Yes
`show_userpic`	No
`return_target`	No
`initial_budget`	No
`idempotency_key`	No
`daily_budget_limit`	No
`impression_frequency`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that this is a provider write, requires confirm=true, and defaults to paused with zero initial budget, but it omits auth/account requirements, rate limits, idempotency behavior, return shape, and whether the ad must later be submitted for review.

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?

Three short sentences are front-loaded with the core purpose, then the write confirmation, then the default state. There is no filler and every sentence adds useful information.

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?

This is a complex create operation with 16 parameters, a nested target object, no annotations, no output schema, and zero schema description coverage. The description provides important guard/default context but is far too sparse to fully guide correct invocation.

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% across 16 parameters. The description only clarifies confirm and the paused/budget defaults; it says nothing about essential parameters like title, promote_url, cpm, placement, target, account_id, idempotency_key, or budget-related fields.

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 states a specific verb and resource: create one Telegram Ads advertisement through the official API. This distinguishes it from sibling operations such as increasing budget, submitting for review, or setting paused status, which act on existing ads.

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 clear invocation context: this is a provider write and confirm=true is required. It does not name explicit alternatives or when-not conditions, but the operational precondition is clear.

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

Deploy Server