Crawlora MCP

telegram_post

Read-only

Get one public Telegram channel post by username and post id and return its text, links, publish time, edited flag, views, reactions, reply and forward references, media thumbnails and link-preview card. Use this when you already know a post link such as t.me/durov/531 (the id is the final number); a missing, deleted or non-public post returns not found. 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>",
      "id": "<id>"
    },
    "name": "telegram_post"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Post id, from a post link or telegram-channel-posts' own posts[].id field
`username`	Yes	Public channel 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.3/5.0

Behavior4/5

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

Annotations already establish read-only and open-world behavior, and the description adds useful failure semantics: missing, deleted, or non-public posts return not found. It also lists the response contents and includes a legal usage restriction, though it does not discuss rate limits or pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with purpose and return contents, followed by usage and error behavior. It is dense but every sentence adds relevant information, with no redundant 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?

Given the output schema, annotations, and 100% parameter coverage, the description supplies the remaining context an agent needs: exact usage condition, input-link format, error behavior, and output overview. Nothing essential is missing for correct invocation.

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%, so both parameters are already documented. The description reinforces the link format and that the id is the final number, but adds little parameter meaning beyond what the schema provides.

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?

The description uses a specific verb and resource: 'Get one public Telegram channel post by username and post id.' It also enumerates the returned content, making clear this is a single-post retrieval tool rather than a channel-listing or channel-info sibling.

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?

It clearly states when to use the tool: when you already know a post link such as t.me/durov/531, with the id as the final number. It does not explicitly name telegram_channel_posts or telegram_channel as alternatives, but the 'already know a post link' condition effectively implies the distinction.

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?