Skip to main content
Glama
Sign In
telegram-bot-mcp

telegram-bot-mcp

by FantomaSkaRus1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

forward_messages

Forward multiple messages from one chat to another. Control silent sending, content protection, and topic targeting.

Instructions

Forward 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": "forward_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idNoTarget chat ID. Optional — defaults to log group
message_idsYesJSON array of message IDs to forward
from_chat_idYesSource chat ID
protect_contentNoProtect from forwarding
message_thread_idNoTopic/thread ID for supergroups with topics enabled
disable_notificationNoSend silently

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.3

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral details such as whether forwarded messages preserve sender, formatting, or attachments, and any limits on batch size. The description only states the basic action, leaving important behavior unspecified.

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?

The description is a single concise sentence that gets directly to the point. However, it is perhaps too brief; a bit more detail could be added without harming conciseness.

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 lack of output schema and annotations, the description should provide more context about return values, effects on messages, and any constraints. It is currently too minimal for a tool with six parameters.

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 individual parameter descriptions. The tool description adds no further meaning beyond the schema, so the baseline score of 3 applies.

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 verb 'forward' and resource 'multiple messages', and it implicitly distinguishes from the sibling 'forward_message' (singular) by specifying 'multiple'. The action and scope are unambiguous.

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 is provided on when to use this tool versus alternatives like 'copy_messages' or 'forward_message'. The description does not mention when forwarding is preferred over copying or any prerequisites.

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

Deploy Server

Other Tools