Crawlora MCP

telegram_group

Read-only

Get a public Telegram group's profile and return its title, description, member count and, when shown, how many members are online. Use this to size or identify a public group by username (or t.me link); only the profile is available, not the group's messages. A channel name returns an error pointing to telegram_channel, and bots, user accounts and invite links are rejected. Results must not be used to train AI or machine-learning systems.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "username": "<username>"
    },
    "name": "telegram_group"
  }
}

Input Schema

Name	Required	Description	Default
`username`	Yes	Public group username, with or without @ or a t.me link

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only cover read-only and open-world access. The description adds real behavioral detail beyond that: profile only and never messages, an error redirecting channel lookups to telegram_channel, rejection of bots/users/invite links, and a licensing restriction on training use.

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 return values, then usage, then failure modes. Dense and largely waste-free, though the trailing training-data restriction sentence is policy rather than tool behavior and adds length without aiding invocation.

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?

An output schema exists, so return values needn't be restated, yet the description covers scope (profile only), accepted inputs, and the error/rejection paths an agent is likely to hit. Nothing needed 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.

Parameters4/5

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

Schema coverage is 100% and already documents that the username may include @ or a t.me link, so the description mostly restates it; it does reinforce the accepted input forms in prose. Slight credit above the baseline 3 for confirming the link form is accepted at call time.

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 group's profile') plus exactly what comes back: title, description, member count and online count. It also draws an explicit boundary against the sibling telegram_channel, so an agent can distinguish it without opening either schema.

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?

Gives the intended use ('size or identify a public group'), the accepted identifier forms, and explicit exclusions: channels route to telegram_channel, and bots, user accounts and invite links are rejected. That is when/when-not guidance with a named alternative.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?