Fast MCP Telegram

by ru.l1979.tg-mcp

Send message

send_message

Destructive

Send text and optional file attachments to a Telegram chat. Supports reply-to (including forum topics and channel discussion groups), parse_mode: classic markdown/html/auto (entities) or rich (Rich Message document; dialect auto-detected). parse_mode=rich cannot be combined with files. File attachments as http(s) URLs, local paths, or data: URIs. When files are provided, the message text becomes a caption. For channel posts with reply_to_id, automatically posts in the linked discussion group. Success: dict with message_id, date, chat, text, status='sent', and sender info (rich messages also set rich=true and rich_format). Error: dict with ok=false and error string. Use send_message to create new messages; use edit_message to modify existing ones. Use send_message_to_phone when targeting a phone number instead of a chat_id. Full documentation: https://github.com/alexeyleshchenko/fast-mcp-telegram/blob/main/docs/Tools-Reference.md

Input Schema

TableJSON Schema

Name	Required	Description	Default
`files`	No	List of attachment URLs, local paths, or data URIs (one or more strings). data: URIs (data:<mime>;base64,<payload>) work in all server modes; local paths work in stdio mode only.
`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.
`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
`reply_to_id`	No	Telegram message id to reply to. For forums, topic root id; for channel posts, post id (may create a comment). Omit for a new top-level message.

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

A5/5.0

Behavior5/5

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

Annotations are minimal (openWorldHint, destructiveHint), so the description carries the burden. It discloses key behavioral details: parse_mode='rich' cannot combine with files, text becomes caption when files are present, channel post reply_to_id auto-posts in discussion group, and precise success/error dict shapes. 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?

Although longer than two sentences, every sentence carries necessary information. The description is front-loaded with the core action, then layers details logically (format, files, reply, channel behavior, result, alternatives). There is zero fluff; redundant details are delegated to a documentation link.

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?

This is a complex tool with 5 parameters, an output schema, and nontrivial edge cases (parse modes, file handling, reply-to variations, discussion groups). The description covers all of these and also states the success/error return structures, making it complete for selecting and invoking correctly.

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?

Schema coverage is 100%, giving a baseline of 3, but the description adds significant value: it explains file source types (URLs, local paths, data: URIs), parse_mode dialect detection, reply_to_id semantics for forums/channels, and how 'me' works for chat_id. This goes well beyond the schema's own descriptions.

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 opens with 'Send text and optional file attachments to a Telegram chat' – a specific verb, resource, and scope. It clearly distinguishes send_message from edit_message and send_message_to_phone by naming them and stating their different use cases.

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 when-to-use guidance: 'Use send_message to create new messages; use edit_message to modify existing ones. Use send_message_to_phone when targeting a phone number instead of a chat_id.' It also covers channel reply behavior and parse_mode rules.

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?