Skip to main content
Glama

ADS Beast

telegram_ads_status

Read-only

Connected Telegram Ads accounts, their goal and currency, and what is automated versus done by hand.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "telegram_ads_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
client_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 structurally. The description contributes some content context by noting it reports both account metadata and what is automated versus manual, but it says nothing about authentication requirements, whether all connected accounts are returned by default, or how large the result set may be.

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 tight sentence with no filler, and the content is front-loaded on the resource being described. It is slightly under-specified rather than verbose, which is a completeness issue more than a structural one.

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

Completeness2/5

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

With no output schema and an undocumented parameter, the description carries the full burden and does not deliver: the caller does not learn the shape of the response, whether automation status is a boolean or description, or how client_id affects the result. For a discovery/status tool that is meant to precede publishing, that is a meaningful gap.

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

Parameters2/5

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

The single optional client_id parameter has 0% schema description coverage and the description never mentions it, so there is no way to tell whether passing it scopes the result to one client or filters something else. With one undocumented parameter and no compensating text, it falls below the baseline that a fully covered schema would earn.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description reads as a noun phrase naming the resource ("Connected Telegram Ads accounts, their goal and currency") rather than a verb+resource statement of retrieval, so the action (fetch/read) must be inferred from the tool name. It does hint at the returned content (goal, currency, automation status), but it never distinguishes this from chatgpt_ads_status or explains how it relates to the publishing/targeting siblings.

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 when-to-use or when-not-to-use guidance at all — nothing says to call this before telegram_ads_publish_task or telegram_ads_draft_generate, nor whether it is a prerequisite check. The agent must guess the call context 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.