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

telegram-bot-mcp

by FantomaSkaRus1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

edit_message_media

Edit media content of a sent message. Update image, video, or animation via InputMedia JSON, with optional new caption.

Instructions

Edit media content of a previously sent message. Pass a JSON string as media parameter with InputMedia object.

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": "edit_message_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaYesJSON string with InputMedia object (type, media, caption, etc.)
chat_idNoChat ID or @channel_username. Optional — defaults to log group
message_idNoID of the message to edit (required if inline_message_id not provided)
reply_markupNoJSON string with inline keyboard markup
inline_message_idNoInline message ID (required if chat_id/message_id not provided)

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 exist, so the description must fully disclose behavior. It does not state whether the media is replaced or appended, any time limits for editing, or how the tool handles conflicts with other message components like captions.

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 concise with two sentences, no superfluous content. However, it could be more structured to include important usage notes without increasing length significantly.

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 complexity of 5 parameters and no output schema or annotations, the description is insufficient. It omits information about conditional requirements (e.g., message_id vs inline_message_id) and the effect of optional parameters like reply_markup.

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% with descriptions for all parameters. The description adds minimal value beyond the schema by specifying that the media parameter must be a JSON string with InputMedia object, but this is already implied by the schema description.

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 ('Edit media content'), the target resource ('a previously sent message'), and distinguishes from sibling tools like edit_message_caption or edit_message by focusing specifically on 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 is provided on when to use this tool versus alternatives (e.g., edit_message, edit_message_caption) or when not to use it. The description merely gives a brief parameter instruction.

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