Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

telegram_group

Fetch a public Telegram group profile by username, @handle, or t.me link and return title, description, member count, and online count. Public groups only; messages and invite links are unsupported.

Instructions

Get a public Telegram group profile. Returns the public profile of a Telegram group from its public t.me page: title, description, member count and, when Telegram shows it, the number of members online. username is the group's public username, with or without a leading @ or a t.me link. Only the profile is available for groups; their messages are not readable here. Channels (use telegram-channel), bots, user accounts and invite links are not supported and return an error that says which kind of name was given; a username nobody owns returns not found. online is 0 when Telegram shows no online figure. avatar_url is omitted for groups without a profile photo. Only public content is read, 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 group username, with or without @ or a t.me link

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.6/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden and does: it discloses that messages are not readable here, that unsupported name kinds return an error naming the kind, that unknown usernames return not found, that online is 0 when absent, and that avatar_url is omitted without a photo. It also flags the terms-of-service restriction on using content for AI training.

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 purpose and return fields, then scope limits, then edge cases, then the terms notice — a logical order. It is on the long side and the avatar_url/online notes are dense, but each sentence carries a distinct behavior rather than filler.

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?

There is no output schema, yet the description enumerates the returned fields (title, description, member count, online, avatar_url) and their null/omission semantics. Combined with error behavior and scope exclusions, an agent has everything needed to call it and interpret results.

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 the schema's own parameter description already states 'with or without @ or a t.me link', so the description largely restates it. No additional validation, length, or case-sensitivity guidance is added, so baseline 3 applies.

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 and resource ('Get a public Telegram group profile') and explains the source (public t.me page). It explicitly distinguishes itself from telegram-channel, telegram-bot, telegram-post and invite links, so an agent can pick it without opening other schemas.

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

Usage Guidelines5/5

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

Explicitly says when to use it (public group usernames, with or without @ or t.me link) and when not to (channels → use telegram-channel; bots, user accounts, invite links unsupported), including the failure mode for each.

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