Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

telegram_bot

Fetch a public Telegram bot's profile by username to get its name, verified status, description, avatar link, and monthly user count; detect channels, groups, or unknown usernames.

Instructions

Get a public Telegram bot's profile. Returns a public Telegram bot's profile from its t.me page: name, verified flag, description, avatar link and, when Telegram shows it, the number of monthly users. username is the bot's public username, with or without a leading @ or a t.me URL prefix. A channel, group, person's account or invite link is reported as such so you can use the right endpoint; an unknown username returns not found. Only public profile text is read.

Input Schema

NameRequiredDescriptionDefault
usernameYesBot username, with or without a leading @ or a t.me URL prefix

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.16

TDQS

A4.4/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 burden and mostly succeeds: it discloses the data source (t.me page), the read-only public-text scope, the conditional presence of monthly users, and the not-found behavior for unknown usernames. It omits rate limits or failure modes for t.me blocking, keeping it below 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?

Content is dense and front-loaded with the return fields and routing rule stated up front. The opening sentence pair is slightly redundant ('Get a public Telegram bot's profile. Returns a public Telegram bot's profile...'), which costs a point but does not obscure anything.

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 required parameter and no output schema, the description fully covers input formats, returned fields, entity-type mismatch reporting, and not-found behavior. Nothing an agent needs to call 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 description coverage is 100% and the schema already documents the @ and t.me URL prefix flexibility, so the description's repetition of that detail adds no new meaning beyond the structured field.

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 bot's profile) and enumerates the returned fields, which immediately distinguishes it from telegram_channel, telegram_group and 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 Guidelines5/5

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

Explicitly says that a channel, group, person's account or invite link is reported as such so the agent can switch to the right endpoint, giving both the when-to-use and the when-not-to-use condition.

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