Skip to main content
Glama

ADS Beast

telegram_ads_policy_check

Read-only

Checks a sponsored message against Telegram's prohibited categories, the 160-character text limit, the title limit and the link format.

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_policy_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
cpmNoCPM bid in the account currency.
textYesSponsored message text.
titleNoInternal ad name, up to 128 bytes.
currencyNoAccount currency: EUR, TON or XTR.
client_idNo
promote_urlNoWhat is promoted: @username, t.me link, bot or website.
website_nameNoSite name, required when an external site is promoted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds which rules are evaluated but says nothing about output shape (pass/fail, violation list) or whether the check is local or fetches Telegram's live policy — the latter matters given openWorldHint. Useful but not rich.

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 front-loaded sentence enumerating the checks with zero filler; every clause carries information an agent can act on.

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?

With 7 parameters (only one required), no output schema, and no explanation of how the remaining optional fields (cpm, currency, client_id, website_name) affect the check, the description leaves gaps. For a read-only validation tool with annotations covering safety, it is adequate but an agent still cannot predict the result payload.

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

Parameters4/5

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

Schema coverage is 86%, so the baseline is 3, but the description contributes real constraint information absent from the schema: the 160-character text limit, a title limit, and link-format rules that bear on promote_url. It does not clarify the non-validated optional fields (cpm, currency, client_id, website_name), so it stops short of full marks.

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?

States a specific verb ('Checks') and object ('sponsored message') and enumerates the four rule families applied (prohibited categories, 160-char text limit, title limit, link format). This clearly separates it from telegram_ads_draft_generate and the sibling chatgpt_ads_policy_check, though it does not name an alternative explicitly.

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?

No explicit when-to-use or when-not guidance; the intent (validate a sponsored message before publishing) is only implied by the verb 'Checks' and the sibling set. An agent can infer it is a pre-publish validation step, but nothing states prerequisites or what to do if it fails.

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.