Skip to main content
Glama
germankingerman-byte

Telegram MCP Server

by germankingerman-byte
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

Send Telegram Message

telegram_send_message

Send text messages to Telegram chats, groups, channels, or users via bot for notifications and updates.

Instructions

Send a text message to a Telegram chat, group, channel, or user via the bot.

This is the primary tool for pushing notifications, alerts, or updates into Telegram — e.g. from a scheduled routine or automation.

Args:

  • chat_id (string | number): Target chat ID or '@channel_username'

  • text (string): Message body, 1-4096 characters

  • parse_mode ('Markdown' | 'MarkdownV2' | 'HTML' | 'none'): Text formatting (default: 'none')

  • disable_notification (boolean): Send silently (default: false)

  • reply_to_message_id (number, optional): Reply to a specific earlier message

Returns: Confirmation text including the chat and the new message_id (needed later to edit/delete/pin it).

Error Handling:

  • "chat not found" -> the chat_id is wrong, or the user has never started a chat with the bot. Ask the user to send /start to the bot first, or use telegram_get_updates to find the right chat_id.

  • 403 Forbidden -> the bot was blocked by the user or removed from the group/channel.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesMessage text to send, e.g. 'Deploy finished successfully ✅'
chat_idYesTarget chat. Use a numeric chat ID (e.g. 123456789 for a user, -1001234567890 for a supergroup/channel) or a public channel username with a leading '@' (e.g. '@my_channel'). If unknown, call telegram_get_updates after the user messages the bot to discover it.
parse_modeNoText formatting mode. 'HTML' supports <b>, <i>, <a href>, <code>, <pre>. 'MarkdownV2' requires escaping special characters (_*[]()~`>#+-=|{}.!) with a backslash. 'none' sends plain text.none
reply_to_message_idNoIf set, sends this message as a reply to the given message_id in the same chat
disable_notificationNoIf true, sends the message silently (no notification sound for recipients)

Tool Definition Quality

A4.5/5.0
Behavior5/5

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

The description goes beyond annotations by detailing the return value (confirmation with message_id), error scenarios (chat not found, 403 Forbidden), prerequisites (user must start chat), and effects (message sent). This comprehensively discloses the behavioral traits of the tool.

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?

The description is well-structured with clear sections (purpose, args, returns, errors). It is concise, front-loaded with the purpose, and every sentence adds value. No redundancy or fluff.

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 (5 params, 2 required, no output schema), the description covers usage, parameter details, return value, error handling, and prerequisites (user must start chat). It is fully adequate for an agent to 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?

The input schema has 100% coverage with detailed descriptions for all 5 parameters. The description largely repeats this information without adding significant extra meaning beyond clarifying usage via examples (e.g., 'from a scheduled routine'). 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 'Send a text message to a Telegram chat, group, channel, or user via the bot.' It uses a specific verb+resource and distinguishes from sibling tools like telegram_send_photo and telegram_send_document by focusing on text messages and positioning itself as the primary tool for notifications.

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 provides context: 'primary tool for pushing notifications, alerts, or updates into Telegram — e.g. from a scheduled routine or automation.' It implicitly suggests when to use this tool but does not explicitly exclude alternatives or mention when to use siblings. Error handling offers guidance on recovery, strengthening usage advice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/germankingerman-byte/telegram-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server