Telegram MCP — Next Generation

Edit Text of Sent Telegram Message

edit_message

Idempotent

Replace the text of a message you previously sent in any Telegram chat by specifying the chat, message ID, and new text. Correct typos or update content without resending.

Instructions

Edit the text content of an existing message previously sent by this account. Mutation operation requiring TELEGRAM_SEND_ENABLED=true. Cannot edit messages sent by other users.

Input Schema

TableJSON Schema

Name	Required	Description
`account`	No	Optional account label for multi-account environments. If omitted in single-mode, the default account is used. In multi-mode without an account, read-only tools fan out across all configured accounts.
`chat_id`	Yes	Target Telegram chat, group, supergroup, channel, or user identifier. Accepts numeric chat ID (e.g. -1001234567890 or 123456789), username (e.g. '@channel'), or phone number.
`new_text`	Yes	New replacement text content when editing an existing sent message.
`message_id`	Yes	Unique integer ID of the target message within the specified chat.
`parse_mode`	No	Text formatting parser: 'markdown' (default), 'html', or 'none'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv4.2.0Sep 19, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate a non-read-only, non-destructive, idempotent operation. The description adds valuable behavioral context beyond annotations: it identifies the operation as a mutation and discloses the configuration prerequisite (TELEGRAM_SEND_ENABLED=true) plus the ownership restriction. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two dense sentences with no filler. The main action and target are front-loaded, followed immediately by the critical mutation and permission constraints. Every sentence earns its place.

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 mutation tool with 5 parameters, an output schema, and all parameters fully documented, the description covers the essential operational constraints: mutation status, environment flag, and message ownership. It is complete enough for an agent to select and invoke the tool correctly.

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 description coverage is 100%, so the schema already documents all parameters thoroughly. The description complements this with the ownership constraint but does not add substantial semantic detail beyond what the schema provides. Baseline 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 states a specific verb ('Edit'), a precise resource ('text content of an existing message'), and a key scope constraint ('previously sent by this account'). This immediately differentiates the tool from siblings like send_message, reply_to_message, and delete_message.

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 description gives clear context for when this tool applies: editing an existing message sent by this account, and explicitly rules out editing messages sent by other users. It does not name sibling alternatives, but the scope and the TELEGRAM_SEND_ENABLED prerequisite provide adequate usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.