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

telegram-bot-mcp

by FantomaSkaRus1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

edit_business_message_text

Update the text of an existing business message. Specify message ID, chat ID, and new text; optionally set formatting or inline keyboard.

Instructions

Edit a text message sent on behalf of a business account.

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": {
      "business_connection_id": "<business_connection_id>",
      "chat_id": "<chat_id>",
      "message_id": "<message_id>",
      "text": "<text>"
    },
    "name": "edit_business_message_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesNew message text
chat_idYesChat ID of the message
message_idYesID of the message to edit
parse_modeNoText formatting mode
reply_markupNoJSON string with inline keyboard markup
business_connection_idYesBusiness connection ID

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?

No annotations available; the description only states the action without disclosing behavioral traits like permanence, permission requirements, or rate limits.

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, front-loaded sentence that efficiently conveys the tool's purpose without unnecessary words. However, it may be too brief.

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 6 parameters and no annotations or output schema, the description is insufficient. It does not mention return values, required parameters, or limitations.

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%, so the baseline is 3. The description does not add any additional meaning beyond what the schema already provides.

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 'edit', the resource 'text message', and the context 'on behalf of a business account', which distinguishes it from siblings like edit_business_message_caption or edit_business_message_media.

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 provided on when to use this tool vs alternatives such as edit_message or edit_business_message_caption. No mention of prerequisites or when not to use it.

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