Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

telegram_channel

Fetch public Telegram channel or group details by handle or t.me URL, returning channel information from its web preview.

Instructions

telegram: Channel Details. GET /v1/telegram/channel. Provide one of: handle, url. Get public Telegram channel or group details from its web preview. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "handle": "<handle>"
    },
    "name": "telegram_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesPublic Telegram handle, @handle, or t.me channel URL.
cache_max_ageNoUse a cached response this old or newer for 0 credits. If none is available, fetch live at the endpoint’s normal price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden well by disclosing that this is a GET operation, costs 1 credit on success, and that errors, blocked/timeout requests, invalid requests, and cache hits cost nothing. It still omits authentication requirements, rate-limit behavior, and the shape of returned details, and the not-found/empty-result charging sentence is somewhat vague.

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?

The description is reasonably front-loaded: it starts with the purpose and endpoint, then gives input guidance, then billing behavior. The cost sentences are longer than necessary, and the 'handle, url' guidance is wrong, but overall the structure is efficient and readable.

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 simple two-parameter tool, the description covers endpoint, purpose, and billing behavior, but it does not explain what channel details are returned and includes an inconsistent url parameter claim. Since there is no output schema or annotations, those omissions and inaccuracies leave meaningful gaps.

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?

Schema coverage is 100%, so the schema itself explains handle and cache_max_age clearly, but the description says 'Provide one of: handle, url' even though the schema accepts only handle and cache_max_age and has no url parameter. That inaccurate parameter guidance can mislead an agent and reduces the value of an otherwise schema-complete definition.

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 specific resource and action: get public Telegram channel or group details from a web preview, via GET /v1/telegram/channel. It distinguishes itself implicitly from sibling tools like telegram_channel_posts and telegram_post by focusing on channel/group-level details rather than posts, though it does not explicitly name alternatives.

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?

It implies usage by saying to provide a handle or URL and that it returns public channel or group details, but it gives no explicit when-to-use versus when-not guidance and does not name sibling alternatives. The usage context is understandable but not fully directive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools