Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Telegram channel posts

telegram_channel_posts_get
Read-onlyIdempotent

Retrieve recent posts from a public Telegram channel by username to monitor updates or collect content. Use the returned cursor to page through older posts; groups are not supported.

Instructions

List recent posts from a public Telegram channel. Groups are not supported. Requires handle. Returns a list (use cursor when paginated).

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_posts_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque pagination cursor from a previous response. Omit for the first page.
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds a scope restriction (public channels only, no groups) and notes the result is a list with cursor pagination. It says nothing about rate limits, auth requirements, or what happens with private/restricted channels beyond the group exclusion.

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, front-loaded with the resource and scope, with no filler. Slightly terse in that the pagination and group-exclusion notes are compressed into fragments.

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 read-only list tool with full schema coverage and no output schema, the definition covers scope, prerequisites and pagination adequately. Return shape is not described, but annotations and schema carry most of the remaining burden.

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%, so both the cursor and handle parameters are already documented in detail, and the description only restates the handle requirement. The cursor hint ('use cursor when paginated') adds minor usage context beyond the schema but little new meaning.

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 ('List recent posts from a public Telegram channel') and immediately scopes it with 'Groups are not supported.' An agent can distinguish it from the single-post sibling telegram_channel_post_get, though 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 Guidelines3/5

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

Provides a meaningful exclusion ('Groups are not supported') and a prerequisite ('Requires handle'), which tells the agent when the tool is not applicable. However, it offers no guidance on choosing between this tool and the more specific telegram_channel_post_get, and no alternatives are named.

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