telegram-bot-mcp

send_media_group

Send a group of photos or videos as an album to a Telegram chat, with options for protection, reply, and notification settings.

Instructions

Send a group of photos or videos as an album. If chat_id is omitted, sends to the default log group.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "media": "<media>"
    },
    "name": "send_media_group"
  }
}

Input Schema

Name	Required	Description
`media`	Yes	JSON array of InputMedia objects (2-10 items). Each must have type and media.
`chat_id`	No	Chat ID or @channel_username. Optional — defaults to log group
`protect_content`	No	Protect messages from forwarding/saving
`reply_parameters`	No	JSON object with ReplyParameters (e.g. {"message_id": 123})
`message_thread_id`	No	Topic/thread ID for supergroups with topics enabled
`disable_notification`	No	Send silently without notification

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.0.3Mar 5, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description provides minimal behavioral info: it sends an album and defaults chat_id to log group. It does not disclose limits (e.g., 2-10 items) or error handling, which are in schema but not description. Some context added but not rich.

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 a single, clear sentence with no extraneous words. It front-loads the core purpose and is immediately understandable, earning its place.

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

Completeness2/5

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

Despite good schema coverage, the description omits what the tool returns (no output schema) and lacks details about errors or permissions. For a 6-parameter tool, more context is needed for complete agent understanding.

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 coverage is 100%, so the baseline is 3. The description only restates the schema note about default chat_id, adding no new parametric insight. Thus, it meets the baseline without adding value.

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 sends a group of photos or videos as an album, distinct from sending individual media. It also notes the default log group behavior, making the purpose specific and unambiguous.

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 implies usage for sending media albums, contrasting with siblings like send_photo or send_video. However, it does not explicitly state when not to use this tool or list alternatives, though the context is clear.

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

Deploy Server