Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

telegram_channel

Fetch a public Telegram channel profile by username to view its title, description, verification badge, subscriber count, and content counters from the public web preview.

Instructions

Get a public Telegram channel profile. Returns the public profile of a Telegram channel: title, description, verification badge, subscriber count, and the photo, video, file and link counters shown on the channel's public web preview (t.me/s/{username}). username is the channel's public username, with or without a leading @ or a t.me link; private channels, groups, bots, user accounts and invite links are not supported and return an error that says which kind of name was given. subscribers is the exact figure when available; subscribers_approximate is true when only the preview's abbreviated figure (for example 10.3M) could be read. The photo, video, file and link counters are the preview's abbreviated figures and are approximate for large channels. Only public content is read, no media files are returned, and 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
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.2/5.0
Behavior4/5

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

No annotations, so the description carries the full burden and does substantial work: discloses that only public content is read, no media files are returned, counters are approximate (with subscribers_approximate semantics), errors identify the name type, and a usage restriction on AI training. Missing auth/rate-limit details keeps it from a 5.

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?

Front-loaded with the core purpose and return fields, then caveats. Slightly dense, with mild redundancy between the opening 'Get a profile' and 'Returns the public profile', but every sentence carries substantive information.

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 one parameter, no output schema, and no annotations, the description fills the gap by detailing return fields, approximation behavior, error behavior, and legal constraints. Nothing an agent needs to invoke it correctly is missing.

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% and already documents username. The description adds value by clarifying accepted forms (@, t.me link) and that unsupported name kinds produce a descriptive error, but does not extend much beyond the schema field. Baseline 3 is appropriate.

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?

States a specific verb+resource ('Get a public Telegram channel profile') and enumerates exactly the fields returned (title, description, verification badge, subscriber count, media counters). It even distinguishes from what it is not (groups, bots, user accounts), so an agent can separate it from telegram_channel_posts or telegram_group.

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?

Explicitly states supported input forms (username with/without @ or t.me link) and enumerates unsupported cases (private channels, groups, bots, invite links) that return an error. It doesn't name sibling tools as alternatives, but the inclusion/exclusion guidance is clear.

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