Skip to main content
Glama
wazap-mcp

wazap-mcp

by razvangirgiz

Delete a WhatsApp message

delete_message
DestructiveIdempotent

Delete or retract a WhatsApp message for everyone within two days or remove it from linked devices only; confirm with the user before proceeding.

Instructions

Delete a message; confirm with the user first. for_everyone: true retracts it for everyone within 2 days: the account's own message, or anyone's in a group where it is admin. for_everyone: false removes any message from the linked account's devices only.

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>",
      "for_everyone": "<for_everyone>"
    },
    "name": "delete_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNo
message_idYes
for_everyoneYes

Output Schema

NameRequiredDescriptionDefault
account_idYes
message_idYes
for_everyoneYes

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 / for_everyone / description
      Removed value: -"Required. true retracts it for everyone in the chat; false deletes it for the linked account only"
    • removedInput schema / properties / message_id / description
      Removed value: -"Message id from read_messages / search_messages / get_message, e.g. \"false_4072...@s.whatsapp.net_3EB0...\""
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "account_id": {
      +      "type": "string"
      +    },
      +    "for_everyone": {
      +      "type": "boolean"
      +    },
      +    "message_id": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "message_id",
      +    "for_everyone",
      +    "account_id"
      +  ],
      +  "type": "object"
      +}
  4. Changed3 schema fields changedv0.21.0
    • removedInput schema / properties / for_everyone / default
      Removed value: -false
    • changedInput schema / properties / for_everyone / description
      Previous value: -"Retract for all participants (WhatsApp supports no other kind of delete here)"New value: +"Required. true retracts it for everyone in the chat; false deletes it for the linked account only"
    • changedInput schema / required
      Previous value: -[
      -  "message_id"
      -]New value: +[
      +  "message_id",
      +  "for_everyone"
      +]
  5. 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"
      +}
  6. First observedv0.9.3

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructive, openWorld and idempotent, but the description adds constraints annotations cannot express: the 2-day retraction window, the ownership/admin permission model, and the device-only blast radius when for_everyone is false. These are exactly the operational facts an agent needs before committing a destructive action.

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?

The purpose and the confirm-first instruction are front-loaded, and each clause carries real information. The middle sentence is dense and slightly over-packed with the mode, window and permission rules in one run-on, but nothing is wasteful.

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 destructive 3-parameter tool with an output schema, the description covers the critical risk surface: eligibility, time limits and scope of effect. It stops short of stating what happens on failure (e.g. retraction attempted beyond 2 days) and whether account_id is optional/defaulted, both of which an agent would benefit from knowing.

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 coverage is 0%, so the description must carry parameter meaning. It does this thoroughly for for_everyone, explaining the semantics and scope of both boolean values, and mentions the 'linked account' context for account_id, but message_id (with its minLength of 5) and the account_id default/selection behavior remain undocumented.

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?

The description opens with a specific verb and resource ('Delete a message') and immediately distinguishes the two modes of deletion, retraction for everyone versus removal from the linked account's devices only. An agent can tell this apart from edit_message or send_message from the first clause alone.

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 procedural rule ('confirm with the user first') and states the eligibility conditions for the for_everyone: true path: within 2 days, and either the account's own message or a group where it is admin. It does not name alternatives such as editing a message instead of deleting, so it falls short of explicit when-not guidance.

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