Skip to main content
Glama
ramich2077

tgreader-mcp

by ramich2077

read_messages

Retrieve messages from a Telegram channel by username or ID. Filter by date, limit, or regex pattern to get specific content.

Instructions

Read messages from a Telegram channel.

Args: channel: Channel @username or numeric ID. account: Account name (default: configured default account). limit: Max messages when offset_date is None (default 20, max 1000). offset_date: ISO 8601 datetime — read all messages before this date (capped at 1000). search: Optional RegExp pattern to filter message text (max 200 chars).

Returns JSON: {"count": N, "channel": {"id", "title", "username"}, "messages": [{"id", "date", "text", "views", "reactions", "media_type", "link"}]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelYes
accountNo
limitNo
offset_dateNo
searchNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Describes limits (default 20, max 1000 for limit/cap), offset_date behavior, search regex, and return structure. No annotations, so description reasonably covers non-destructive read operation.

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?

Well-structured with Args and Returns sections, front-loaded purpose, no redundant text. Each sentence adds value.

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?

Covers all 5 parameters, describes return format, includes relevant constraints (max limits, default account). Output schema exists but description provides additional context for completeness.

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?

Adds meaning beyond schema: explains limit default and max, offset_date as 'before', search as 'RegExp pattern max 200 chars', and account default. Schema has 0% description coverage, so description compensates well.

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?

Clearly states 'Read messages from a Telegram channel' with specific verb and resource. Distinguishes from sibling 'list_channels' by focusing on message content vs channel listing.

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?

Implicitly clarifies use case (reading messages) vs sibling (listing channels), but lacks explicit when-not or alternative conditions. Still clear enough for typical usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ramich2077/tgreader-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server