Skip to main content
Glama

Turbo Notify: WhatsApp for AI agents

Delete a message for everyone

delete_message
Destructive

Revoke a WhatsApp message for everyone in the conversation.

This is WhatsApp's "delete for everyone". It is not reversible, and recipients see a tombstone where the message was, so they can tell something was deleted. Confirm with a human before using it on anything a person has plausibly already read.

The number first appears online and its unread messages in that conversation are marked as read, then the message is deleted. Opening the conversation this way is automatic and uses no quota of its own.

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

Input Schema

NameRequiredDescriptionDefault
message_idYesMessage id (`msg_…`), as returned by a send or by `list_messages`.
number_aliasNoWhich of the organization's WhatsApp numbers this acts on: `main`, the alias of an extra number, or the number's `id` (`num_…`), which stays the same when the alias is renamed. Call `list_numbers` to see them. Defaults to the main number.main

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/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 real context beyond them: the action is irreversible, recipients see a tombstone and can tell something was removed, and the number is brought online with unread messages marked as read as a side effect. These are exactly the behavioral facts an agent needs before committing to an unquotaed side-effecting mutation.

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?

Front-loaded with the core action, then irreversibility, then the human-confirmation rule — a sensible ordering with little waste. The final paragraph is awkwardly worded ('The number first appears online and its unread messages... are marked as read') and needs a re-read to parse, which costs it a point.

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?

An output schema exists, so return values need no explanation, and the description covers what matters for a destructive tool: reversibility, recipient-visible effects, the read/online side effect, and a confirmation policy. Authority requirements are the only notable omission, and the annotations already flag the open-world destructive nature.

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 and number_alias are already fully documented, and the description adds no syntax or format guidance for either. The only marginal addition is the implicit link between the number being brought online and the `number_alias` target, which is a side effect rather than parameter meaning. Baseline 3 applies.

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 ('Revoke a WhatsApp message') plus the scope that defines it ('for everyone in the conversation'), immediately separating it from a per-device delete or an edit. The follow-up sentence pins the WhatsApp-specific meaning, so an agent can distinguish it from siblings like edit_text_message without opening either 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 conditional guardrail: confirm with a human before deleting anything a recipient has 'plausibly already read', which effectively defines the risky-use case. However, it never points to an alternative action (e.g., editing the text or reacting) for situations where deletion is too heavy-handed, so routing between siblings is left to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.