Deletes multiple Telegram messages in a single chat at once, up to 100 per call. Specify the chat ID or @username plus message IDs to remove them together.
Delete multiple messages at once. Max 100 messages.
| Name | Required | Description | Default |
|---|---|---|---|
| chat_id | Yes | Chat ID or @username | |
| message_ids | Yes |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and readOnlyHint=false, so the description need not restate that deletion is destructive. It adds a useful constraint (Max 100 messages), but provides no additional context about permissions, irreversibility, or behavior when some message IDs are invalid—an acceptable minimum given annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two short sentences, front-loaded with the action and resource, and every word adds value. There is zero redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-parameter batch deletion tool, the description covers the core action and limit, but omits potential details like required permissions or error behavior. Given the simplicity and existing annotations, it's minimally viable but not fully complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already provides descriptions for 'chat_id' (Chat ID or @username) and sets min/max items on 'message_ids'. The description reinforces the batch aspect ('multiple', 'Max 100'), but does not add significant new meaning beyond the schema constraints. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('Delete') and resource ('multiple messages'), clearly distinguishing this batch tool from the sibling 'delete_message' for single deletions. The 'at once' qualifier clarifies the tool's batch nature, and 'Max 100 messages' adds a precise scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'Delete multiple messages at once' clearly establishes the use case for batch deletion, distinguishing it from single-message deletion tools. While it does not explicitly name alternatives or exclusion cases, the context is clear enough for an agent to select this tool over individual delete_message.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.