WhatsApp Business API by Wassenger

manage_whatsapp_queue

Comprehensive WhatsApp queue management tool supporting all queue operations. Perfect for monitoring queue health, controlling message delivery flow, and performing bulk message operations. Supports all WhatsApp queue operations through a unified action-based interface.

Available actions:

get_status: Get comprehensive queue statistics and status information
update_status: Update queue processing status (pause/active/reject/freeze) with optional force delivery
delete_messages: Delete queued messages with flexible filtering options. A call with no messageIds, phoneNumbers, groupIds or dateRange would delete every queued and scheduled message, so it is refused unless confirmEmptyQueue is true

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": {
      "device": "<device>",
      "action": "<action>"
    },
    "name": "manage_whatsapp_queue"
  }
}

Input Schema

Name	Required	Description
`force`	No	Force delivery of all queued messages with no delay for 30 minutes (only works with "active" or "reject" status)
`action`	Yes	Action to perform on WhatsApp queue
`device`	Yes	WhatsApp device ID connected to Wassenger (24 character hexadecimal string)
`status`	No	Queue processing status (required for update_status action)
`filters`	No	Filtering options for selective message deletion (for delete_messages action)
`confirmEmptyQueue`	No	Set to true only to delete every queued and scheduled message of the number (scheduled ones are kept if filters.skipScheduled is true). delete_messages refuses a call without messageIds, phoneNumbers, groupIds or a dateRange unless this is true
`waitForCompletion`	No	Wait until all messages are deleted (may take up to 90 seconds for large queues)

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 28, 2026

addedInput schema / properties / confirmEmptyQueue

Added value: +{
+  "default": false,
+  "description": "Set to true only to delete every queued and scheduled message of the number (scheduled ones are kept if filters.skipScheduled is true). delete_messages refuses a call without messageIds, phoneNumbers, groupIds or a dateRange unless this is true",
+  "type": "boolean"
+}

addedInput schema / properties / filters / properties / groupIds / minItems
```
Added value: +1
```
addedInput schema / properties / filters / properties / messageIds / minItems
```
Added value: +1
```
addedInput schema / properties / filters / properties / phoneNumbers / minItems
```
Added value: +1
```

First observedOct 26, 2026

TDQS

A3.5/5.0

Behavior4/5

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

No annotations exist, so the description carries the full burden and does disclose the most important trait: that a filterless delete_messages deletes every queued and scheduled message and is refused unless confirmEmptyQueue is true. It does not cover permission/auth requirements or what happens to in-flight messages on pause/freeze, leaving some behavioral surface undocumented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The action list is well-structured and front-loads the destructive caveat, but the opening three sentences repeat the same claim ('comprehensive ... supporting all queue operations' twice) and the 'Perfect for...' marketing line earns little space. Roughly a third of the text is redundant.

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?

For a 7-parameter tool with nested filter objects and no output schema and no annotations, the description should explain roughly what get_status returns and how status transitions affect delivery; instead it only says 'comprehensive queue statistics', which is too vague to substitute for the missing output schema.

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% and each parameter (force, status, filters, confirmEmptyQueue, waitForCompletion) is already documented in the schema. The description only restates that update_status takes an optional force delivery and delete_messages takes flexible filters, adding no syntax or constraint detail beyond the schema, so baseline 3 applies.

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?

States a specific resource domain (WhatsApp queue) and enumerates the three supported actions with one-line summaries, so an agent knows exactly what surface the tool covers. It doesn't name a sibling to differentiate from, but the queue domain is unique among siblings, which makes the boundary inferable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The action list gives per-action context ('monitoring queue health', 'controlling message delivery flow', 'bulk message operations') and includes a real guardrail for delete_messages. However there is no explicit when-not-to-use guidance and no reference to alternatives such as send_whatsapp_message or manage_whatsapp_channel_messages, so routing is implied rather than stated.

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

All WhatsApp Business API by Wassenger tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.