Skip to main content
Glama
telegram-channels-mcp

telegram-channels-mcp

read_messages

Read-only

Fetch recent messages or posts from a Telegram channel, group, or private chat; use offset_id to page to older messages and max_chars to limit text length.

Instructions

Read the latest messages or posts of a channel, group or private chat, newest first. chat: @username, t.me link or numeric id from list_chats. For older messages pass offset_id = the smallest id you already got. Text longer than max_chars is cut, use 0 for full text

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": {
      "chat": "<chat>"
    },
    "name": "read_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
limitNo
max_charsNo
offset_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this a read-only, open-world, non-destructive operation, so the bar is lower; the description still adds real context: result ordering (newest first), truncation of long text against max_chars, and the offset_id paging contract. It says nothing about rate limits, what happens when offset_id is beyond the channel start, or empty results, which are the remaining behavioral gaps.

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?

Three short sentences plus a fragment, front-loaded with the operation and ordering, then parameter guidance, with no filler. Some phrasing is over-compressed to the point of ambiguity ('Text longer than max_chars is cut' could be misread as discarded rather than truncated).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter read tool with an output schema (so return values need no explanation) and annotations covering safety, this is nearly complete: input formats, paging, and truncation are all covered. The only shortfall is the undocumented 'limit' parameter and the lack of a one-line steer toward search_messages.

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 description coverage is 0%, so the description carries the full burden and mostly does: it explains the accepted formats for 'chat', the meaning of offset_id, and the max_chars/0 convention. The 'limit' parameter is never mentioned beyond its default of 20, leaving its meaning (message count, max value) undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description pairs a specific verb ('Read') with a specific resource ('latest messages or posts of a channel, group or private chat') and states the ordering ('newest first'). It does not explicitly contrast itself with the sibling search_messages, so an agent must infer that this is the chronological-read tool and the other is the query tool.

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?

Strong operational guidance: the chat parameter format is spelled out ('@username, t.me link or numeric id from list_chats'), pagination is explained ('pass offset_id = the smallest id you already got'), and the full-text escape hatch is given ('use 0 for full text'). It stops short of explicitly saying when to prefer search_messages over this tool, which keeps it out of the top band.

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