wazap-mcp

Edit a WhatsApp message you sent

edit_message

DestructiveIdempotent

Replace the text of a WhatsApp message your linked account sent within 15 minutes; after that window, send a correction instead.

Instructions

Replace the text of a message the linked account sent. WhatsApp allows it for 15 minutes after sending; later, send a correction instead.

Input Schema

Name	Required	Description	Default
`text`	Yes
`account_id`	No
`message_id`	Yes

Output Schema

Name	Required	Description	Default
`text`	Yes
`chat_id`	Yes
`timestamp`	Yes
`account_id`	Yes
`message_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv1.6.0Oct 22, 2026
- removedInput schema / properties / account_id / description
```
Removed value: -"Account id"
```

Changed4 schema fields changedv1.0.3Sep 23, 2026

changedInput schema / properties / account_id / description

Previous value: -"Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account."New value: +"Account id"

removedInput schema / properties / message_id / description
```
Removed value: -"A message the linked account sent"
```
removedInput schema / properties / text / description
```
Removed value: -"The replacement text"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "account_id": {
+      "type": "string"
+    },
+    "chat_id": {
+      "type": "string"
+    },
+    "message_id": {
+      "type": "string"
+    },
+    "text": {
+      "type": "string"
+    },
+    "timestamp": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "message_id",
+    "chat_id",
+    "text",
+    "timestamp",
+    "account_id"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv0.15.0Sep 12, 2026

addedInput schema / properties / account_id

Added value: +{
+  "description": "Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.",
+  "minLength": 1,
+  "type": "string"
+}

First observedv0.9.3Aug 23, 2026

TDQS

A4/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 description's job is lighter; it still adds the genuinely non-obvious 15-minute window and the ownership constraint. It doesn't say what happens on a rejected/timeout edit or whether the original text is recoverable, which would be the remaining useful detail for a destructive mutation.

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 filler, with the ownership scope and the time constraint front-loaded before the fallback advice.

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

Completeness3/5

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

Output schema and annotations carry much of the load, and the time/ownership constraints are the key behavioral facts. However, for a destructive, open-world mutation with completely undocumented parameters, an agent is left guessing about account_id semantics and the failure modes of an expired or foreign message.

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 0%, so the description must carry parameter meaning. It conveys only that a message and its replacement text are involved, leaving account_id (optional, presumably the linked account selector) and the format/constraints of message_id undocumented anywhere.

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 precise verb+resource ('Replace the text of a message') and narrows scope to messages 'the linked account sent', which cleanly separates it from send_message, delete_message, and react_to_message in the sibling list.

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 an explicit eligibility window ('15 minutes after sending') and a fallback action ('send a correction instead'). It stops short of naming the sibling to use for the fallback, so the routing is implied rather than explicit.

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