Skip to main content
Glama
FantomaSkaRus1

telegram-bot-mcp

edit_business_message_media

Edit the media (photo, video, audio, document) of an existing business account message. Provide the business connection, chat, message ID, and new media JSON.

Instructions

Edit media content of a message sent on behalf of a business account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mediaYesJSON string with InputMedia object (type, media, caption, etc.)
chat_idYesChat ID of the message
message_idYesID of the message to edit
reply_markupNoJSON string with inline keyboard markup
business_connection_idYesBusiness connection ID
Behavior2/5

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

With no annotations, the description must disclose behavioral traits but only states the basic action. Limitations (e.g., supported media types, error conditions) are not mentioned.

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 single sentence is concise and front-loaded, but it could include more structured detail without becoming verbose.

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 no output schema, no annotations, and 5 parameters, the description is insufficient. It lacks information about return values, side effects, or prerequisites.

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%. The description adds no additional meaning beyond the schema's parameter descriptions, so a baseline score of 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 uses a specific verb ('Edit') and resource ('media content of a message') with context ('on behalf of a business account'), clearly distinguishing it from sibling tools that edit captions or text.

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 like edit_message_media or send a new message. The description lacks explicit context for appropriate use.

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/FantomaSkaRus1/telegram-bot-mcp'

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