Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Telegram channel

telegram_channel_get
Read-onlyIdempotent

Retrieve metadata for a public Telegram channel or group by username to identify and verify its details. Provide the public handle with or without the leading @.

Instructions

Get metadata for a public Telegram channel or group by username. Requires handle.

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "telegram_channel_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesRequired. Telegram public username (channel or group), with or without leading @.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds one useful constraint — only *public* channels/groups are reachable — but says nothing about failure modes (private/nonexistent handles), rate limits, or what 'metadata' contains, which matters since there is no output schema.

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?

Two short sentences, purpose front-loaded with the qualifier second. The trailing 'Requires `handle`' sentence duplicates schema information and earns little space, which keeps it from a 5.

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 single-resource read with full schema coverage and a complete annotation set, the essentials are present. However, with no output schema, the description never characterizes the returned metadata fields, and it gives no guidance on the stateful conversation_id handshake beyond what the schema states.

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 description coverage is 100% and all four parameters, including the analytics-only llm_model and conversation_id plumbing, are documented in the schema. The description only restates the handle requirement, adding no syntax or format detail beyond what structured data already provides.

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 and resource: fetching metadata for a public Telegram channel or group keyed by username. The word 'metadata' implicitly separates it from the sibling post-listing tools (telegram_channel_post_get, telegram_channel_posts_get), but no sibling is named explicitly.

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 guidance, no exclusions, and no named alternative. 'Requires `handle`' merely restates the schema's required field rather than telling the agent when this tool is the right choice over the post-fetching siblings.

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