Turbo Notify: WhatsApp for AI agents

Edit the text of a message already sent

edit_text_message

Destructive

Replace the text of a text message this number already sent.

The recipient sees the new text marked as edited. The message keeps its id and its place in the conversation; only the text changes.

Only a text message can be edited here. For the caption of an image, video or document use edit_media_caption, and for a calendar event edit_calendar_event or cancel_calendar_event. A location, contact card, link button, sticker or audio message cannot be edited at all: delete_message is the only change for them. Using this tool on any message that is not text 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 text 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.

Input Schema

Name	Required	Description	Default
`text`	Yes	The new text. It replaces the whole text of the message.
`message_id`	Yes	Message id (`msg_…`), as returned by a send or by `list_messages`.
`number_alias`	No	Which 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

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only flag destructive/non-idempotent/open-world; the description goes far beyond by disclosing the 15-minute acceptance window, the exact error codes returned (message_not_editable, edit_window_expired), the asynchronous outcome via message.edited / message.edit.failed events, and the side effect of bringing the number online and marking unread messages as read at no quota cost. That is exactly the operational context an agent needs before calling a mutation.

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?

Well structured into short paragraphs, front-loaded with the core action, and nearly every sentence carries a distinct constraint or behavior. It runs slightly long, and the closing paragraph on presence/read marking is tangential to the edit itself, though still operationally useful.

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?

An output schema exists, so return values need not be explained, yet the description still clarifies that the call returns acceptance rather than the outcome and routes the agent to list_events for results. Combined with the constraint coverage, nothing needed to call 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 description coverage is 100%, so message_id, text, and number_alias are already documented in the schema. The description restates that only the text changes and keeps the id, but adds no format, default, or alias-resolution guidance beyond what the schema provides. Baseline 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?

Uses a specific verb and resource ('Replace the text of a text message this number already sent') and immediately delimits scope against named siblings (edit_media_caption, edit_calendar_event, delete_message). An agent can distinguish this from every adjacent tool 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 text messages, only messages sent through Turbo Notify, not phone-typed or received messages, and only within 15 minutes. It names the correct alternative for each unsupported case, including the fallback to send_text after the window expires.

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

All Turbo Notify: WhatsApp for AI agents tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.