Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

telegram_channel

Read-only

Get a public Telegram channel's profile and return its title, description, verification badge, exact subscriber count, and photo, video, file and link counters. Use this with a channel username (or t.me link) to size or identify a channel; private channels, groups, bots and user accounts are not supported and return an error naming which kind of name was given. 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_channel"
  }
}

Input Schema

NameRequiredDescriptionDefault
usernameYesPublic channel username, with or without @ or a t.me link

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint and openWorldHint, so the description need not cover safety. It adds genuine value beyond them: the exact error behavior for unsupported name kinds and the scope of returned data. It omits rate limits and pagination, which keeps it below 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 verb and returned fields, then scope limits. Efficient overall; the AI-training restriction is a licensing term rather than invocation guidance, so it is the one sentence that doesn't directly earn its place.

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, a full output schema, and read-only annotations, the description covers everything needed: supported input forms, return contents, and the error path for unsupported accounts. Nothing material for correct invocation 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 the schema already states the username accepts '@' or a t.me link, so the description's '(or t.me link)' adds no new meaning. Baseline 3 applies when the schema carries parameter documentation.

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 (Get) and resource (a public Telegram channel's profile) and enumerates exactly what is returned: title, description, verification badge, subscriber count, and media/link counters. A reader can distinguish it from telegram_channel_posts, telegram_group, and telegram_post without opening a schema.

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 says to use a channel username or t.me link 'to size or identify a channel' and enumerates exclusions (private channels, groups, bots, user accounts) that return an error. It stops short of naming the sibling tools to reach for instead, but the exclusion list effectively routes the agent.

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

All Crawlora MCP toolsInspect
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