fast-mcp-telegram

by io.github.leshchenko1979

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

TDQS

A4.7/5.0

Behavior5/5

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

Adds behavioral details beyond annotations: limitations (only own messages, text only), parse_mode specifics, and return format for both success and error cases. Aligns with annotations and provides deeper understanding.

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?

Concise yet information-dense. Every sentence adds value: purpose, constraints, parse_mode, return format, usage guidance, and doc link. Front-loaded with the main action.

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?

The description covers all necessary aspects: what it does, when to use, behavioral limitations, parameter context, and return values. With output schema present, this is fully complete for an agent to use 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 already provides 100% coverage including detailed descriptions for each parameter. The description adds little beyond schema, but it does mention parse_mode in context and return format, which slightly enhances understanding. 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 clearly states 'Replace the text of an existing message in a Telegram chat' with specific verb and resource. It distinguishes from siblings by mentioning 'Use edit_message to update a previously sent message; use send_message to create new ones.'

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?

Explicitly states when to use this tool vs send_message, and includes constraints like only works on own messages and cannot edit media. This provides clear usage guidance.

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.

TDQS

A4.3/5.0

Disambiguation5/5

Each tool serves a distinct purpose: sending vs editing messages, per-chat vs global search, finding vs retrieving chat info, and a low-level API escape hatch. No two tools overlap in functionality.

Naming Consistency4/5

Tool names follow a consistent verb_noun pattern in snake_case (e.g., send_message, get_chat_info). Minor deviation with 'search_messages_globally' (adverb inserted) and 'invoke_mtproto' (different verb), but overall pattern is clear.

Tool Count5/5

8 tools is a well-scoped set for a Telegram assistant. It covers core operations without being overwhelming or too sparse.

Completeness3/5

Covers send, edit, read, search, and chat discovery. Missing delete and forward message tools, but the low-level invoke_mtproto can compensate. Notable gaps in common messaging workflows.

Edit message

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources