Skip to main content
Glama

ADS Beast

telegram_ads_draft_generate

Builds a ready-to-submit Telegram ad within the 160-character limit with bid, budget and an impressions estimate, and reports whether it passes preflight. Amounts are in the Telegram account currency.

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": {
      "text": "<text>"
    },
    "name": "telegram_ads_draft_generate"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpmNoCPM bid in the account currency.
textYesAd text.
titleNoShort title.
budgetNoBudget in the account currency.
buttonNoButton for a website ad.
currencyNoEUR, TON or XTR.
client_idNo
placementNochannel_post, bot_banner, search_result or video_banner.
autoshortenNoCut the text at a word boundary when it is too long.
promote_urlNo@username, t.me link, bot or website.
website_nameNoSite name for an external link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the mutation profile is already known; the description adds genuine value on top by disclosing the 160-character constraint, that amounts follow the Telegram account currency, and that the call returns an impressions estimate plus a preflight pass result. It stops short of saying whether a failed preflight raises an error or merely reports, and mentions no auth or rate-limit 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?

A single dense sentence with zero filler: the character limit, bid/budget inputs, estimate output, preflight verdict, and currency rule each carry distinct information. The core purpose is front-loaded before the qualifiers.

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?

With 11 parameters, no output schema, and a mutation annotation set, the description does the needed extra work by describing what comes back (impressions estimate, preflight verdict) and the currency convention. Remaining gaps are minor for a draft-creation tool: the notion of "preflight" is undefined and nothing says which parameter combinations are required per placement.

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 91%, so the schema already documents nearly every field and the baseline is 3. The description contributes the unit semantics for the monetary fields ("Amounts are in the Telegram account currency") and ties the 160-character cap to the text/autoshorten parameters, but adds nothing about placement, button, or promote_url usage.

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?

"Builds a ready-to-submit Telegram ad within the 160-character limit with bid, budget and an impressions estimate, and reports whether it passes preflight" gives a specific verb (builds/drafts), a specific resource (Telegram ad), and enumerates the concrete artifacts produced. It implicitly separates itself from policy-check and publish siblings by being the drafting step, though it never names them outright.

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?

The "ready-to-submit" and "passes preflight" phrasing implies this is the step before publishing or a policy check, but no explicit when-to-use, when-not-to-use, or alternative is stated. An agent must infer the position of this tool in the workflow from the sibling names rather than from the description.

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.