Skip to main content
Glama
Sign In
mcp-telegram-agent

mcp-telegram-agent

by a19901201
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

delete_message

Removes a specific bot-sent Telegram message by ID, letting agents clean up or retract messages they previously sent.

Instructions

Delete a specific message by ID (can only delete messages sent by the bot).

刪除指定 ID 的訊息（僅能刪除機器人自己發送的訊息）。

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": {
      "message_id": "<message_id>"
    },
    "name": "delete_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idNo
message_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.7

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the meaningful behavioral fact: only bot-authored messages can be removed. It does not say whether deletion is permanent, whether it removes the message for all participants, or what error surfaces when the restriction is violated. Those are real gaps for a destructive mutation, though the ownership constraint is the single most valuable disclosure.

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?

The constraint is front-loaded in a single tight sentence with no filler. The full bilingual duplication doubles the length for the same content, which is defensible for an internationalized tool set but is repeated text rather than added information.

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?

An output schema exists, so return values need not be explained, and the central restriction is covered. What remains missing is the role of chat_id (unexplained in both schema and description) and any failure behavior for non-bot messages, which matters for a destructive operation with zero annotation coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 2 parameters, so the description must compensate and largely doesn't. It references the message ID but adds no format or semantics beyond the parameter name, and chat_id — which is nullable and seemingly optional despite the API typically needing it — is never mentioned at all.

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+resource ('Delete a specific message') plus the identifying parameter ('by ID'), and immediately scopes it with a hard constraint ('can only delete messages sent by the bot'). Against a sibling set composed entirely of send_* and edit_message_text tools, the delete action 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 Guidelines4/5

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

The bot-ownership restriction gives an explicit exclusion (when NOT usable), which is the most important routing rule for this tool. It does not name alternatives or explain what to do when a message was not sent by the bot, so it falls short of full when/when-not/alternatives guidance.

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