Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

telegram_channel_posts

Read-only

List posts from a public Telegram channel, 20 per page newest first, and return each post's id, link, text, publish time, views, reactions, replies, forwards, media thumbnails and link-preview card. Use this to read or monitor a channel's history; pass before with the previous response's next_before to page backwards, or query to search inside the channel. A search with no matches returns an empty list. 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_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSearch term to look for inside the channel, up to 128 characters
beforeNoReturn only posts with an id lower than this; use the previous response's next_before. Omit for the newest page
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.5/5.0
Behavior5/5

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

Annotations already mark the tool as read-only and open-world, and the description adds valuable behavioral detail: page size, newest-first ordering, `next_before` pagination, and empty-list behavior on no matches. It also discloses a usage restriction about not training AI systems, going well beyond what annotations provide.

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 definition is front-loaded with the core operation and pagination behavior, then covers search and edge cases. Every sentence contributes useful context, and there is no 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 an output schema, annotations, and full parameter descriptions, the description supplies all remaining operational context an agent needs: pagination direction, search behavior, page size, and empty-result handling. 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 coverage is 100%, and the schema already documents `username`, `query`, and `before` in detail. The description repeats the pagination and search roles but adds no new syntax, constraints, or meaning beyond the schema.

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 — listing posts from a public Telegram channel — and defines scope by saying it returns channel history with 20 posts per page. It is clearly distinct from a single-post or channel-metadata sibling, so an agent can identify its function without opening the 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?

It clearly states the intended use case: reading or monitoring a channel's history. It explains how to page backwards with `before` and how to search inside the channel with `query`, though it does not explicitly compare itself to sibling tools like `telegram_post` or `telegram_channel`.

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