Skip to main content
Glama
overpod

MCP Telegram

telegram-delete-topic

Destructive

Delete a forum topic and its entire message history from a supergroup. Provide the chat ID and topic ID to remove the topic permanently.

Instructions

Delete a forum topic and all its message history

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chatIdYesChat ID or username of the forum supergroup
topicIdYesTopic ID to delete
Behavior4/5

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

Annotations already provide destructiveHint=true and readOnlyHint=false. The description adds the detail that it deletes 'all its message history', confirming the destructive scope. This adds value beyond annotations, though it doesn't mention irreversibility or side effects like removing associated data.

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?

The description is a single concise sentence with no wasted words. It immediately communicates the core functionality.

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

Completeness3/5

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

Given the tool's destructive nature, two parameters, and no output schema, the description covers the essential action and scope but lacks guidance on prerequisites, return values, or error conditions. It is adequate but not comprehensive.

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 coverage is 100%—both parameters (chatId, topicId) have descriptions that explain their purpose. The tool description does not add any additional meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 clearly states the verb 'Delete' and the resource 'forum topic', and specifies 'all its message history' to clarify scope. This distinguishes it from siblings like telegram-delete-message (deletes individual messages) and telegram-edit-topic (edits topics).

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

Usage Guidelines2/5

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

The description does not provide any when-to-use guidance, prerequisites, or alternatives. It lacks explicit context such as requiring the chat to be a forum or the topic to exist, and does not mention when not to use this tool.

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/overpod/mcp-telegram'

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