Skip to main content
Glama

ADS Beast

telegram_ads_targeting

Read-only

Languages, topics with their ids and countries, read from Telegram Ads itself for one connected account.

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>"
    },
    "name": "telegram_ads_targeting"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idYesADS Beast ad account id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: the data is read live from Telegram Ads itself rather than a cached table, and is scoped to one connected account. It stops short of noting failure modes (e.g. unconnected account) or response shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single compact sentence with no filler, and the enumerations of what is returned are front-loaded. Phrasing like 'topics with their ids' is slightly awkward but costs nothing in clarity.

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?

There is no output schema, so the description carries the burden of explaining returns; it lists the data categories but not their structure (separate lists, id-keyed maps, nesting). For a simple single-parameter read tool with annotations this is adequate but leaves an agent guessing at the response shape.

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?

With one parameter at 100% schema coverage the schema already documents account_id fully, so the baseline applies. The description's phrase 'for one connected account' reinforces that the id selects a specific linked account and that results are account-scoped, which is a small but genuine addition.

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 names a specific resource set — languages, topics with their ids, and countries — and pins the source as Telegram Ads for a single connected account. That is far more concrete than a tautology, though it is a noun phrase with no verb, so the retrieval action is inferred from 'read' at the end rather than stated up front.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit statement of when to call this versus alternatives, no prerequisite check that the account must be connected, and no mention of how the returned ids feed into ad drafting or policy checks. Usage is only weakly implied by the description's framing.

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.