whatsapp-mcp

Overview Schema Source Related Servers Discussions Admin

edit_message

DestructiveIdempotent

Change the text of a sent WhatsApp message within 15 minutes; the updated text replaces the original for all recipients.

Instructions

Modifie le texte d'un de mes messages, dans les 15 minutes qui suivent son envoi. L'ancien texte est remplacé chez tous les destinataires.

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": {
      "chat": "<chat>",
      "message_id": "<message_id>",
      "text": "<text>"
    },
    "name": "edit_message"
  }
}

Input Schema

Name	Required	Description
`chat`	Yes
`text`	Yes	Nouveau texte.
`account`	No
`message_id`	Yes

Output Schema

Name	Required	Description	Default
`at`	Yes
`chat_jid`	Yes
`message_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Oct 20, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely useful context beyond them: the 15-minute edit window and the fact that the replacement propagates to all recipients ('L'ancien texte est remplacé chez tous les destinataires'). It omits what happens on failure past the window (e.g., error vs. silent no-op).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero padding, with the temporal constraint front-loaded alongside the core action. Every clause earns its place.

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

Completeness4/5

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

For a mutation tool, the description supplies the two things an agent most needs beyond the rich annotations: the 15-minute window and the recipient-visible replacement. An output schema exists, so return values need not be explained. The unaddressed 'account' and 'chat' semantics are the remaining gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% — just the 'text' field is documented ('Nouveau texte.'). The description does not explain 'chat', 'message_id', or the multi-account 'account' parameter, so it fails to compensate for the coverage gap in a 4-parameter tool.

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?

States a specific verb and resource ('Modifie le texte d'un de mes messages') and immediately scopes it with a hard constraint (within 15 minutes of sending). An agent can distinguish it from send_message (creates) and delete_message (removes) without opening another schema.

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

Usage Guidelines4/5

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

Gives a clear precondition — only the user's own messages, only within 15 minutes of sending — which tells the agent when this tool is even applicable. It does not, however, route to an alternative for the out-of-window or own-message-only failure cases.

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