telegram-mcp

Overview Schema Source Related Servers Discussions Admin

list_forum_topics

Retrieve forum topics from a Telegram supergroup, including id, title, unread count, and flags. Optionally filter by title substring to find specific topics.

Instructions

List topics in a forum supergroup (e.g. GLC). Returns id, title, unread_count, and flags per topic. The General topic is always id 1.

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_id": "<chat_id>"
    },
    "name": "list_forum_topics"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max topics (cap 100)
`query`	No	Optional title substring filter.
`chat_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Aug 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the burden of explaining behavior. It discloses the per-topic return fields and the important invariant that the General topic is always id 1, which is useful behavioral context beyond the schema.

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?

Three short sentences, each carrying distinct value: scope, output, and an invariant. The essential information is front-loaded and there is no fluff.

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 simple listing tool with three parameters and no output schema, the description adequately explains what the tool returns and notes the general topic invariant. It does not mention ordering or pagination behavior, but the schema already specifies the limit cap and the tool's purpose is clear.

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 67%, so most parameter meaning is already provided by the schema. The description adds the example 'GLC' for chat_id and notes that the General topic is id 1, but does not add substantial detail about limit or query beyond what the schema already states.

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 states a specific verb and resource: 'List topics in a forum supergroup', with a concrete example ('GLC'). It also enumerates the return fields, making the tool's function unmistakable and distinct from sibling tools like list_chats.

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 indicates this tool is for forum supergroup topics, which implies when it should be used versus list_chats or chat_info tools. It does not explicitly state exclusions, but the context is strong enough for an agent to select it appropriately.

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