Skip to main content
Glama

ADS Beast

telegram_ads_publish_task

Creates a task for an operator to paste a checked ad into ads.telegram.org by hand. The path for accounts without an API token.

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": {
      "campaign_name": "<campaign_name>",
      "text": "<text>",
      "promote_url": "<promote_url>"
    },
    "name": "telegram_ads_publish_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpmNoCPM bid in the account currency.
textYesAd text.
titleNoShort title.
budgetNoBudget in the account currency.
currencyNoEUR, TON or XTR.
client_idNo
promote_urlYes@username, t.me link, bot or website.
website_nameNoSite name for an external link.
campaign_nameYesCampaign name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so safety is largely covered. The description adds real value by revealing that execution is manual by a human operator rather than an API call, but it omits what happens after queueing — whether anything is actually published, what identifier comes back, and how completion is confirmed.

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?

Two short sentences with zero filler; the core action comes first and the scoping condition follows immediately.

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

Completeness3/5

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

For a 9-parameter task-creation tool with no output schema, the description covers what the tool does and who executes it, but leaves the agent unable to anticipate the return value or the follow-up step for checking the queued task. Adequate, with a clear gap around post-call behavior.

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 89%, so nearly every field is already self-documenting in the input schema. The description adds no field-level meaning (e.g. which fields are ignored for certain promote_url types, or how cpm/budget interact with currency), so the baseline 3 applies.

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 states a concrete verb and object ("Creates a task for an operator to paste a checked ad") and pins the target surface (ads.telegram.org), so the action is unambiguous. It also distinguishes itself by condition ("accounts without an API token") rather than by naming the sibling API-path tool, which is slightly weaker but still decidable.

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?

The qualifier "The path for accounts without an API token" gives an explicit when-to-use condition that routes the agent away from an API-based publish tool. What's missing is an explicit exclusion/alternative name and any prerequisite ordering (e.g. run the policy check first).

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.