Skip to main content
Glama
Sign In
Telegram MCP

Telegram MCP

by Anonymouse8882
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_forum_topics

List topics in a forum supergroup by chat ID or username. Supports filtering by title and limit results to retrieve topic IDs for reading messages.

Instructions

列出话题群（forum）里的话题。拿到 id 后可用 get_messages(topic_id=...) 读该话题。

Args: chat: 开了话题功能的超级群。 limit: 上限，最多 100。 query: 按标题过滤。

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": "get_forum_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
limitNo
queryNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses chat must be a supergroup with topics enabled and limit cap at 100. But it does not specify read-only nature, error behaviors, or permission requirements. Adequate but not fully transparent.

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?

Extremely concise with two short paragraphs. Every sentence adds value, including a usage tip for the next step. No unnecessary information.

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?

Given output schema exists, description adequately covers purpose and parameters. It misses pagination hints or ordering, but for a listing tool with output schema, it's fairly complete.

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 coverage is 0%, but description adds meaningful context for all three parameters: chat (supergroup with topics), limit (upper bound 100), query (filter by title). This compensates for the lack of schema descriptions.

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?

Description explicitly states '列出话题群（forum）里的话题' (list topics in forum), providing a specific verb and resource. It also distinguishes from siblings like create_forum_topic and edit_forum_topic by clarifying it's a listing operation.

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 suggests use case: '拿到 id 后可用 get_messages(topic_id=...) 读该话题' (after getting id, use get_messages to read topic). Provides parameter constraints (max limit 100). However, lacks explicit guidance on when not to use or alternative comparisons beyond the sibling context.

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

Deploy Server

Other Tools