Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Edit the caption of an image, video or document

edit_media_caption
Destructive

Replace the caption of a WhatsApp image, video or document this number already sent.

The recipient sees the new caption marked as edited. The file itself stays exactly as it was and the message keeps its id: only the caption changes. There is no way to replace the file; to send a different one, send a new message with send_media.

Only an image, video or document can be edited this way. Audio and stickers have no caption, and a location, contact card or link button cannot be edited at all: delete_message is the only change for them. For the text of a text message use edit_text_message. Using this tool on any other message answers invalid_request: message_not_editable.

Only a message sent THROUGH Turbo Notify can be edited. One typed on the phone itself belongs to the same number but cannot be edited here, and neither can a message received from someone else.

WhatsApp only accepts a change to a caption within 15 minutes of sending it. A later edit is refused up front with invalid_request: edit_window_expired; send a new message instead.

The edit is accepted at once and the outcome arrives as an event: message.edited when it worked, message.edit.failed when WhatsApp or the platform could not apply it. Read them with list_events.

The number first appears online and its unread messages in that conversation are marked as read, then the edit happens. Opening the conversation this way is automatic and uses no quota of its own.

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": {
      "message_id": "<message_id>",
      "caption": "<caption>"
    },
    "name": "edit_media_caption"
  }
}

Input Schema

NameRequiredDescriptionDefault
captionYesThe new caption, up to 1024 characters. It replaces the whole caption. Writing `@<number>` mentions that person, as in a caption on send.
message_idYesMessage id (`msg_…`), as returned by a send or by `list_messages`.
number_aliasNoWhich of the organization's WhatsApp numbers this acts on: `main`, the alias of an extra number, or the number's `id` (`num_…`), which stays the same when the alias is renamed. Call `list_numbers` to see them. Defaults to the main number.main

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: states the recipient sees an edited marker, the file and message id are preserved, the old caption is wholly replaced, the 15-minute WhatsApp window, and the exact error codes (`message_not_editable`, `edit_window_expired`). It discloses side effects not covered by annotations — the number coming online, unread messages being marked read, and no quota consumption — and explains the asynchronous outcome via `message.edited` / `message.edit.failed` read with `list_events`.

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?

Front-loads the core action in the first sentence and organizes the rest into short, purposeful paragraphs covering immutability, eligibility, timing, and event outcome. It is longer than typical but nearly every sentence carries a distinct constraint; the read-marking paragraph at the end is the least essential.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Although an output schema exists, the description still explains that the mutation is accepted synchronously while the result arrives as an event, which is the key non-obvious behavior. Combined with eligibility limits, timing window, and failure codes, nothing an agent needs to invoke this correctly is missing.

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%, so all three parameters, including `number_alias` and the 1024-character caption bound, are already documented in structured fields. The description reinforces caption-replacement semantics ('It replaces the whole caption') but adds no new meaning beyond the schema and never discusses `number_alias` selection. Baseline 3 applies when the schema carries the parameter burden.

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?

Opens with a specific verb and resource ('Replace the caption of a WhatsApp image, video or document this number already sent') and immediately bounds the scope to media already sent. It explicitly contrasts itself with `send_media`, `edit_text_message` and `delete_message`, so an agent can route correctly without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit when-to-use and when-not-to-use rules: only image/video/document, not audio, stickers, locations, contact cards or link buttons; text messages go to `edit_text_message`; replacing the file requires `send_media`; non-editable messages require `delete_message`. It also names the precondition that only messages sent through Turbo Notify qualify.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.