Skip to main content
Glama
telegram-channels-mcp

telegram-channels-mcp

get_comments

Read-only

Fetch comments under a Telegram channel post and return comment IDs for use when replying to a specific comment.

Instructions

Read comments under a channel post. Comment ids from here are used as comment_id in reply_comment

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": {
      "channel": "<channel>",
      "post_id": "<post_id>"
    },
    "name": "get_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
channelYes
post_idYes
max_charsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds a genuine data-shape fact (returned ids are directly reusable as comment_id), but says nothing about pagination behavior from limit or about max_chars truncating comment text.

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?

Two short sentences with the primary action front-loaded and the cross-tool linkage immediately after; nothing is padded. The second sentence is slightly compressed ('Comment ids from here') but remains intelligible.

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

Completeness2/5

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

An output schema and annotations reduce the descriptive burden, and purpose plus the reply_comment linkage are covered. Still, a four-parameter read tool with 0% schema coverage leaves the agent guessing about result bounds and text truncation, which are exactly the details needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning and it does not. It implies channel/post_id by saying 'under a channel post', but limit (default 50) and especially max_chars (default 1000), which likely truncates comment bodies, are unexplained anywhere in the definition.

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 gives a specific verb and resource: 'Read comments under a channel post', scoping it to a post rather than the whole channel, which distinguishes it from sibling tools like read_messages and search_messages. It stops short of naming those siblings explicitly, so the differentiation is implicit rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is a useful workflow cue: comment ids obtained here feed reply_comment's comment_id parameter, which tells an agent when to reach for this tool mid-flow. However, it never states when to prefer this over the other read-style siblings or any precondition such as the post needing to exist.

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