telegram-bot-mcp

copy_messages

Copy multiple messages between Telegram chats by specifying the source chat and message IDs. Optionally set a target chat or use the default log group.

Instructions

Copy multiple messages from one chat to another.

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": {
      "from_chat_id": "<from_chat_id>",
      "message_ids": "<message_ids>"
    },
    "name": "copy_messages"
  }
}

Input Schema

Name	Required	Description
`chat_id`	No	Target chat ID or @channel_username. Optional — defaults to log group
`message_ids`	Yes	JSON array of message IDs to copy
`from_chat_id`	Yes	Source chat ID or @channel_username
`remove_caption`	No	Remove captions from copied messages
`protect_content`	No	Protect messages from forwarding/saving
`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

B3.1/5.0

Behavior2/5

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

No annotations provided, and the description offers no behavioral details beyond the basic action. Missing information on message preservation, permissions required, error handling, or whether deletion of source messages is possible.

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?

Extremely concise single sentence, no fluff. However, could include a bit more context without losing conciseness, such as a mention of optional target chat ID.

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?

Given the tool's complexity (7 parameters, no output schema, no annotations), the description is too minimal. It omits return value structure, rate limits, prerequisite bot permissions, and behavior differences from forwarding.

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 description coverage is 100% for all 7 parameters, so the baseline is 3. The description adds no extra meaning beyond the schema, leaving parameter intent entirely to the schema definitions.

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 action ('Copy'), the resource ('messages'), and the scope ('multiple... from one chat to another'). It effectively distinguishes from sibling tools like 'copy_message' (singular) and 'forward_messages' (different action).

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as 'copy_message' or 'forward_messages'. No context about prerequisites, supported chat types, or limitations.

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

Deploy Server