Skip to main content
Glama

ADS Beast

prepare_telegram_ad_publish

Prepare creating an ad in Telegram Ads through its API. The ad is created paused. cpm and daily_budget_limit are in the Telegram account's currency. Changes nothing: stores a preview_id (15 min, single use) to show, then execute_prepared_change.

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": {
      "account_id": "<account_id>",
      "title": "<title>",
      "promote_url": "<promote_url>",
      "cpm": "<cpm>",
      "reason": "<reason>"
    },
    "name": "prepare_telegram_ad_publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpmYesCPM bid in the account currency.
textNoAd text, up to 160 characters.
titleYesAd name in the account, up to 128 bytes.
buttonNoButton for a website ad.
reasonYesWhy, with numbers (shown to the approver).
placementNochannel_post, bot_banner, search_result or video_banner.
account_idYesADS Beast ad account id.
promote_urlYes@username, t.me link, bot or website.
website_nameNoSite name for an external link.
language_codesNoChannel languages, up to 8.
daily_budget_limitNoDaily limit in the account currency.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations it discloses meaningful behavior: the ad is created paused, nothing is changed, and the preview_id lives 15 minutes and is single-use. It also explains that cpm and daily_budget_limit are denominated in the account currency. It omits permission/approval requirements and any rate-limit or error behavior.

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, each carrying distinct information: what it does, the paused state, and the preview/execute handoff. The non-mutating guarantee is front-loaded and nothing is wasted.

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

Completeness4/5

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

For an 11-parameter staging tool with no output schema, the description covers the critical facts an agent needs: the staged-approval model, the preview_id lifetime, and currency units. It does not explain the approval/reason flow or what the preview payload contains, but there is no output schema demanding that.

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

Parameters3/5

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

Schema description coverage is 100%, so the input schema already documents every parameter including currency and placement. The description's only added semantic, currency denomination for cpm and budget, restates what the schema says, so it stays at baseline.

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 opens with a specific verb and resource: prepare creating an ad in Telegram Ads via the API, and adds the key qualifier that the ad is created paused. That distinguishes it from an execution tool, though it does not name the other preparation/publish siblings it might be confused with.

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 explicitly states the two-step workflow: this tool changes nothing and stores a preview_id to show, then execute_prepared_change performs the action. That is clear routing guidance, but it gives no exclusions or conditions for choosing it over other ad-creation paths.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.