Skip to main content
Glama
wazap-mcp

wazap-mcp

by razvangirgiz

Edit a WhatsApp message you sent

edit_message
DestructiveIdempotent

Replace the text of a message sent from the linked WhatsApp account 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.

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

Input Schema

NameRequiredDescriptionDefault
textYes
account_idNo
message_idYes

Output Schema

NameRequiredDescriptionDefault
textYes
chat_idYes
timestampYes
account_idYes
message_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.7.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed1 schema field changedv1.6.0
    • removedInput schema / properties / account_id / description
      Removed value: -"Account id"
  3. Changed4 schema fields changedv1.0.3
    • 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"
      +}
  4. Changed1 schema field changedv0.15.0
    • 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"
      +}
  5. First observedv0.9.3

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description's genuine addition is the 15-minute edit window and the restriction to messages the account itself sent. It does not say whether the prior text is unrecoverable, whether recipients see an edit marker, or what happens if the target message was deleted.

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 edit action stated first and the time limit plus fallback trailing it. Nothing could be removed without losing information.

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?

An output schema exists, so return values need not be explained, and annotations cover the mutation semantics. What remains thin is the failure/edge-case behavior (deleted message, media-only messages, account_id expectations), which an agent would likely need at call time.

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 0%, so the description must carry the parameter semantics. It does clarify that "text" is the replacement content and that "message_id" must refer to a message the linked account sent, but it says nothing about message_id formatting or the role/optionality of account_id, leaving a substantive gap for a 3-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Replace the text of a message the linked account sent" names a specific verb (replace) and a scoped resource (a message you sent), which distinguishes it from delete_message and send_message without needing their schemas. It stops just short of 5 because the alternative action is described generically ("send a correction") rather than pinned to a concrete sibling.

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?

It gives a concrete condition for use (within 15 minutes of sending) and an explicit fallback when that condition fails (send a correction instead). Guidance is contextual rather than tied to another tool by name, and it doesn't cover other constraints such as permission or whether media captions qualify.

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