Skip to main content
Glama
thenavidm

telegram-mcp-cli

by thenavidm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete messages

delete
Destructive

Remove one or more Telegram messages permanently, with an option to revoke them for all chat participants.

Instructions

Delete one or more messages. This cannot be undone, and with revoke it removes them for everyone in the chat, not only for you.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
peerYesThe chat the messages are in.
revokeNoDelete for everyone, not just this account. Default true.
confirmNoSet true only when the user asked for exactly this action.
message_idsYesIds to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / confirm / description
      Previous value: -"Must be true for this to run. This cannot be undone, so it is refused without it."New value: +"Set true only when the user asked for exactly this action."
  2. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, but the description adds materially: the action cannot be undone, and with revoke it removes messages for everyone rather than just the caller. That is exactly the consequence information an agent needs before invoking a destructive tool.

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, front-loaded with the operation and immediately followed by the irreversibility warning. No filler, though the second sentence packs two separate consequences together.

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 destructive batch-delete with no output schema, the description covers what matters most: irreversibility and the for-everyone scope of revoke. It leaves permission requirements and the confirm gating unstated, but the structured fields cover those.

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%, so the schema documents peer, revoke, confirm, and message_ids on its own. The description restates revoke's global effect ('removes them for everyone in the chat') but adds no syntax, defaults, or constraints beyond what the schema already provides.

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?

States a specific verb and resource ('Delete one or more messages'), so the agent immediately knows the operation and that it is batched over message_ids. It does not explicitly contrast with siblings like edit or forward, but the scope is unambiguous.

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?

Usage is implied by the irreversibility warning and the revoke explanation, but there is no explicit when-to-use/when-not or pointer to alternatives such as edit. The 'confirm' prerequisite lives only in the schema, not in the description.

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