Skip to main content
Glama

ADS Beast

telegram_ads_verify_channel

Read-only

Whether a channel exists, is public and how many subscribers it has.

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": {
      "username": "<username>"
    },
    "name": "telegram_ads_verify_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYes@username or t.me/username of the channel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/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 the useful detail of what the call reports (existence, public flag, subscriber count), but it does not say what happens for a nonexistent, private, or invalid username — an error, or a negative result — which matters for a verification tool.

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?

One short sentence with zero filler; the useful content (existence, publicness, subscriber count) is front-loaded. It is a sentence fragment lacking an explicit verb, which slightly weakens the opening.

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 one-parameter read-only tool with full schema coverage and annotations, the description covers the essentials of what is returned even though no output schema exists. However, it is silent on failure/uniqueness semantics for missing or private channels, and on whether subscriber count is approximate, leaving real gaps for a verification tool.

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 coverage is 100% and the single parameter's format (@username or t.me/username) is fully documented in the schema, so the baseline of 3 applies. The description mentions only 'a channel' and adds no meaning beyond the schema.

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 the resource (a channel) and the three facts returned: existence, public status, and subscriber count. It is clearly distinguishable from the advertising-campaign siblings, but it is phrased as a noun clause without an explicit verb ('verify' only appears in the title/name), so the action is implied rather than stated.

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 guidance on when this tool should be called versus alternatives, no prerequisite (e.g. must be run before targeting or publishing to a channel), and no statement of when not to use it. The agent must infer the verification use case from the name alone.

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.