Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

telegram_channel_posts

List posts from a public Telegram channel, including text, media thumbnails, reactions, and metadata, with pagination and in-channel search for browsing or finding specific content.

Instructions

List posts from a public Telegram channel. Returns one page of up to 20 posts from a public Telegram channel's web preview (t.me/s/{username}), newest first. Each post has its id, link, text, links found in the text, publish time, edited flag, view count, author signature, forwarded-from and reply references, photo and video thumbnails, link-preview card, and reaction tallies. Page backwards by passing the previous response's next_before as before; has_more is false and next_before is omitted on the last page. Pass query to search inside the channel instead of browsing; search pages use the same before cursor. A search with no matches returns an empty posts list. Views are the preview's abbreviated figures (for example 32.4K) and are approximate above 1,000. Media entries carry thumbnail references only, never playable file URLs. Polls, documents, voice notes and stickers appear as an unsupported media entry. Private channels, groups, bots, user accounts and channels that disabled their web preview are not supported. 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
queryNoSearch term to look for inside the channel, up to 128 characters
beforeNoReturn only posts with an id lower than this; use the previous response's next_before. Omit for the newest page
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.1/5.0
Behavior5/5

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

No annotations are provided, and the description carries the full burden well: one page of up to 20 posts newest-first, pagination semantics (has_more false, next_before omitted), empty search result behavior, approximate abbreviated view counts, thumbnail-only media, unsupported media types, and a terms-of-use restriction. This is unusually specific behavioral detail beyond the 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?

It is front-loaded with the core purpose and uses dense but relevant sentences; every clause about pagination, search, media limitations, and supported channel types earns its place. It is lengthy for a single paragraph but not padded or repetitive.

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?

Without an output schema or annotations, the description still explains the return fields, pagination, search behavior, limitations, and media constraints. It is complete enough for an agent to call and interpret the tool correctly.

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 the three parameters are already documented. The description adds some semantic context—query triggers search mode and before is the previous page cursor—but mostly restates what the schema and parameter descriptions already provide, making the baseline 3 appropriate.

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 first sentence gives a specific verb ('List') and resource ('posts from a public Telegram channel'), and the description scopes it to public web previews rather than groups, bots, or private channels. It does not explicitly name sibling tools such as telegram_channel or telegram_post, so it is clear but not fully differentiated from siblings.

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 states when to use query (search inside the channel instead of browsing), how to paginate with next_before, and explicit exclusions: private channels, groups, bots, user accounts, and channels with disabled previews are unsupported. It never names a sibling tool as an alternative, so the routing guidance is strong but not complete.

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