Fast MCP Telegram

by ru.l1979.tg-mcp

Edit message

edit_message

DestructiveIdempotent

Replace the text of an existing message in a Telegram chat. Only works on messages sent by the authenticated account. Cannot edit media or other message attributes — text only. parse_mode: classic markdown/html/auto or rich (Rich Message; dialect auto-detected). Success: dict with message_id, date, chat, text, status='edited', and edit_date (rich messages also set rich=true and rich_format). Error: dict with ok=false and error string (e.g. message not found or not editable). Use edit_message to update a previously sent message; use send_message to create new ones. Full documentation: https://github.com/alexeyleshchenko/fast-mcp-telegram/blob/main/docs/Tools-Reference.md

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chat_id`	Yes	Target chat: numeric id (e.g. -100…), username without @, or 'me' for Saved Messages.
`message`	Yes	Message text. When sending files, used as caption.
`message_id`	Yes	Message id in this chat to edit (from get_messages or Telegram).
`parse_mode`	No	'markdown'/'html'/'auto': classic entity formatting (auto detects). 'rich': Telegram Rich Message document; dialect auto-detected (known HTML tags outside code → rich HTML, else rich markdown). Default is 'auto'. parse_mode='rich' cannot be combined with files.	auto

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`chat`	No
`code`	No
`date`	No
`rich`	No
`text`	No
`error`	No
`action`	No
`params`	No
`sender`	No
`status`	No
`topic_id`	No
`edit_date`	No
`exception`	No
`operation`	No
`error_code`	No
`message_id`	No
`rich_format`	No
`reply_markup`	No

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed4 schema fields changedJul 28, 2026

changedInput schema / properties / parse_mode / description

Previous value: -"'markdown', 'html', or 'auto' (detect from content). Default is 'auto'."New value: +"'markdown'/'html'/'auto': classic entity formatting (auto detects). 'rich': Telegram Rich Message document; dialect auto-detected (known HTML tags outside code → rich HTML, else rich markdown). Default is 'auto'. parse_mode='rich' cannot be combined with files."

changedInput schema / properties / parse_mode / enum

Previous value: -[
-  "markdown",
-  "html",
-  "auto"
-]New value: +[
+  "markdown",
+  "html",
+  "auto",
+  "rich"
+]

addedOutput schema / properties / rich
```
Added value: +{
+  "type": "boolean"
+}
```
addedOutput schema / properties / rich_format
```
Added value: +{
+  "type": "string"
+}
```

First observedJun 18, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond annotations (openWorldHint, idempotentHint, destructiveHint), the description discloses important behavioral traits: it only works on the authenticated account's own messages, cannot edit media (text-only), explains parse_mode behavior including rich message dialect auto-detection, and describes success/error response structures with specific fields. It also notes that 'parse_mode="rich" cannot be combined with files' in the schema, but the description adds operational context about response formats and error scenarios, significantly enhancing transparency.

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 description is information-dense but well-structured. It starts with the primary purpose, then constraints, parameter semantics, return values, usage guidance, and a documentation link. While slightly lengthy, every sentence provides relevant context. It earns a 4 for being comprehensive without excessive wordiness, though it could be trimmed slightly by omitting the full response schema description if an output schema is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (4 parameters, output schema present, annotations present), the description is remarkably complete. It covers purpose, restrictions, parameter behavior, success/error outputs, and usage guidance. The inclusion of specific error examples and the rich message format details ensures the agent can confidently invoke and interpret results. The documentation link provides additional fallback. This meets the highest standard of contextual completeness.

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

Parameters4/5

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

Schema coverage is 100% with detailed parameter descriptions, so baseline is 3. The description adds value by clarifying that the 'message' parameter is text-only (correcting a potential misinterpretation from the schema's 'When sending files, used as caption'), and it summarizes parse_mode options with the rich dialect auto-detection. This goes beyond pure schema repetition, thus a 4 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 clearly states the tool's function: 'Replace the text of an existing message in a Telegram chat.' It specifies the resource (messages in Telegram chats), the action (replace text), and distinguishes from siblings by explicitly noting 'Use edit_message to update a previously sent message; use send_message to create new ones.' It also clarifies scope limitations: 'Only works on messages sent by the authenticated account' and 'Cannot edit media or other message attributes — text only.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description provides explicit guidance on when to use the tool: 'Use edit_message to update a previously sent message; use send_message to create new ones.' It also implies when not to use it by stating 'Cannot edit media,' effectively directing media editing/sending elsewhere. This is clear and actionable, going beyond mere implication.

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

All Fast MCP Telegram tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?