Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

telegram_post

Fetch a single public Telegram channel post by username and post ID to retrieve its text, links, publish time, media thumbnails, and reaction counts.

Instructions

Get one public Telegram channel post. Returns a single post from a public Telegram channel by username and post id, as Telegram's public embed widget shows it: text, links, publish time, edited flag, views, author signature, forwarded-from and reply references, photo and video thumbnails, link-preview card, and reaction tallies. The post id is the number at the end of a post link (t.me/durov/531 has id 531) or the id field of telegram-channel-posts. A post that does not exist, was deleted, or belongs to a channel that is not public returns not found. Telegram's terms restrict using platform content to train AI or machine-learning systems, so results must not be used for that purpose.

Input Schema

NameRequiredDescriptionDefault
idYesPost id, from a post link or telegram-channel-posts' own posts[].id field
usernameYesPublic channel username, with or without @ or a t.me link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full disclosure burden, and it does well: it enumerates returned fields such as text, links, publish time, edited flag, views, author signature, forwarded/reply references, thumbnails, link previews, and reactions. It also discloses not-found behavior and Telegram's terms restriction. It leaves some operational details unstated, such as rate limits or authentication, but for a public read operation this is still strong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and return shape, followed by id semantics and failure constraints. It is dense but every sentence provides useful information, especially given the absence of an output schema.

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

Completeness5/5

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

With no output schema and no annotations, the description compensates by explaining what the single-post response contains, how to identify the post, and when not-found occurs. For a two-parameter fetch tool, this is complete enough for an agent to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both required parameters. The description adds useful meaning with a concrete id example ('t.me/durov/531 has id 531') and reinforces that username may be a public channel with or without @ or a t.me link, raising it slightly above the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 public Telegram channel post,' and immediately clarifies it returns a single post by username and post id. It also indirectly distinguishes itself from telegram_channel_posts by naming that tool as the source of post ids.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description gives clear usage context: it is for one public channel post, requires the channel username and post id, and explains that ids come from post links or telegram-channel-posts. It also states the public-only constraint and that nonexistent, deleted, or non-public posts return not found, though it does not explicitly frame sibling tools as alternatives for other Telegram needs.

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