Skip to main content
Glama
Sign In
Telegram Bot MCP Server

Telegram Bot MCP Server

by aggeentik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

telegram_delete_message

DestructiveIdempotent

Delete a Telegram channel message permanently using channel ID and message ID. Requires bot delete permissions.

Instructions

Delete a message from a Telegram channel.

Use this tool to permanently remove a message from a channel. The bot must have delete message permissions in the channel.

Args: channel_id: Channel username (e.g., '@mychannel') or numeric chat ID. message_id: The unique identifier of the message to delete. response_format: Response format. Options: 'json' for structured data, 'markdown' for human-readable text. Default is 'markdown'.

Returns: A dictionary containing success status, message_id, and operation status. If response_format='markdown', returns formatted text content.

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

Input Schema

NameRequiredDescriptionDefault
channel_idYes
message_idYes
response_formatNomarkdown

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already indicate destructive and non-read-only. The description adds context about permanent removal, required bot permissions, and the return format (dictionary/markdown). No contradiction with annotations.

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?

Description is front-loaded with a clear purpose sentence. The Args/Returns sections are structured and helpful, though the first two sentences slightly repeat the same idea. Overall efficient.

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?

Covers prerequisites (permissions), parameter details, and return values. Given it's a simple delete operation with an output schema, it is adequately complete. It does not address error scenarios, but that is not necessary at this level.

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

Parameters5/5

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

The input schema provides no descriptions (0% coverage), but the description thoroughly explains each parameter: channel_id format (username or numeric ID), message_id as unique identifier, and response_format options with default. This fully compensates for schema gaps.

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?

Clearly states 'Delete a message from a Telegram channel' with a specific verb and resource. Distinguishes from sibling tools like publish and edit by focusing on deletion. No ambiguity.

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?

Explicitly instructs to 'Use this tool to permanently remove a message from a channel' and notes the required permission. However, it does not name alternative tools or explicitly state when not to use, so it lacks exclusion 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