Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Telegram channel post

telegram_channel_post_get
Read-onlyIdempotent

Fetch a single public Telegram channel post by handle and numeric post ID to retrieve its exact content for verification or analysis. Groups are not supported.

Instructions

Get a single public post from a Telegram channel by handle and post ID. Groups are not supported. Requires handle and postId.

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

Input Schema

NameRequiredDescriptionDefault
handleYesRequired. Telegram public username (channel or group), with or without leading @.
postIdYesNumeric Telegram channel post ID from the public URL.
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so safety and repeatability are covered without the description. The description adds a real scope boundary (public posts only, no groups) but says nothing about rate limits, auth requirements, or what happens with private channels.

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?

Three short sentences, well front-loaded with the core action followed by the scope limit. The final sentence restating required parameters is mildly redundant with the schema's required array.

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

Completeness4/5

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

For a simple single-record read with full schema coverage and a complete annotation set, the description covers what the tool does and its main boundary. It omits nothing an agent needs in order to call it correctly, though it could note the public-only restriction more explicitly for private channels.

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%, so `handle`, `postId`, `context`, `llm_model` and `conversation_id` are all documented in the schema itself. The description's restatement that `handle` and `postId` are required adds nothing beyond the schema's required list, and it gives no format hint (e.g. @-prefix handling) that isn't already there.

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 ("Get a single public post from a Telegram channel") and pins the lookup keys (handle + post ID). "Single" implicitly separates it from the plural sibling telegram_channel_posts_get, but no sibling is named explicitly, so differentiation is inferred 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 Guidelines3/5

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

Provides one clear exclusion — "Groups are not supported" — which blocks a plausible mis-call given that `handle` accepts channel-or-group usernames. However, it names no alternative for the list case (telegram_channel_posts_get) or the group case, leaving the agent to infer routing.

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