Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

telegram_channel_posts

Fetch one page of recent public posts from a Telegram channel or group by handle or URL, with cursor pagination for older posts.

Instructions

telegram: Channel Posts. GET /v1/telegram/channel/posts. Provide one of: handle, url. Get one page of recent public posts from a Telegram channel or group. 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_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoNumeric cursor returned by the previous page. Omit it for the latest posts.
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.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that successful calls cost 1 credit, errors and cache hits cost nothing, and results are public and paginated, but it does not describe authentication needs, rate limits, or the shape of returned posts.

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 compact and mostly front-loads the endpoint and core action. Some phrasing is redundant or awkwardly ordered, such as restating the tool label and placing the parameter note before the purpose, but it remains readable and efficient.

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?

The description covers cost behavior and page scope, and the input schema fully defines the three parameters. However, with no output schema and no annotations, it does not explain what a returned post contains or how pagination results should be interpreted.

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 the schema already documents handle, cursor, and cache_max_age. The description adds little beyond the schema and introduces a slight inconsistency by saying 'Provide one of: handle, url' even though there is no url parameter and the handle field already accepts a t.me URL.

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 verb and resource: 'Get one page of recent public posts from a Telegram channel or group,' with the endpoint GET /v1/telegram/channel/posts. This clearly identifies the tool's function, but it does not explicitly differentiate it from siblings such as telegram_channel or telegram_post.

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?

The description says to provide 'handle, url' and describes the page scope, but gives no explicit guidance on when to use this tool versus alternatives like telegram_channel or telegram_post, nor any when-not conditions. The usage context is only implied by the tool's purpose.

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