Skip to main content
Glama
razvangirgiz

wazap-mcp

by razvangirgiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete a WhatsApp message

delete_message
Destructive

Remove a sent WhatsApp message from the chat for all participants. Only works on your own messages sent within the last 2 days.

Instructions

Retract a message. DESTRUCTIVE and visible to everyone in the chat — confirm with the user first. Only works on messages the linked account sent, and only within 2 days of sending.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoRegistry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.
message_idYesMessage id from read_messages / search_messages / get_message, e.g. "false_4072...@s.whatsapp.net_3EB0..."
for_everyoneNoRetract for all participants (WhatsApp supports no other kind of delete here)

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observedv0.9.3

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds non-obvious behavior the annotations cannot convey: the retraction is visible to everyone in the chat, it is restricted to the sender's own messages, and it has a 2-day eligibility window. That is exactly the extra context needed before 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.

Conciseness5/5

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

Two sentences, zero filler, and the DESTRUCTIVE warning is front-loaded ahead of the constraints. Every clause carries information the agent needs.

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?

For a destructive mutation with no output schema, the description covers the safety profile, the confirmation requirement, the visibility consequence, and the two eligibility constraints — the full set of facts an agent needs to call it responsibly. Annotations and schema fill the remaining structured gaps.

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, account_id, and for_everyone are already fully documented in the schema (including the default-resolution behavior of account_id). The description adds only the sender-restriction fact, which mildly relates to message_id semantics but does not go beyond the schema's own detail.

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 ('Retract a message') and immediately distinguishes the operation from siblings like edit_message or send_message by naming the retraction semantics. An agent can identify the correct tool without opening any 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 operational conditions: only messages the linked account sent, only within 2 days of sending, and a required user confirmation before invoking. These are the precise conditions under which the tool succeeds or must be avoided.

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

Deploy Server

Other Tools