WhatsApp Business API by Wassenger

get_whatsapp_devices

Comprehensive tool to retrieve WhatsApp devices with flexible filtering options. Supports all device query scenarios: get all devices, filter by status/session status, search by terms, get only active/online devices, etc.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_whatsapp_devices"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number for pagination (0-based)
`limit`	No	Maximum number of devices to retrieve
`search`	No	Search term: phone number, alias, or device ID
`status`	No	Filter by device operational statuses
`minUptime`	No	Minimum session uptime in seconds (for online devices)
`activeOnly`	No	Only include active/operational devices (authorized, verified, operative)
`exactMatch`	No	Whether to use exact match for search (only applies when search is provided)
`onlineOnly`	No	Only include devices that are currently online
`sessionStatus`	No	Filter by session connectivity statuses
`includeMetrics`	No	Include device metrics (chat counts, contacts, etc.)
`includeSettings`	No	Include device settings and configuration
`includeSessionLogs`	No	Include recent session logs
`includeSessionDetails`	No	Include detailed session information

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: 'retrieve' implies a read, but there is no statement about permissions, rate limits, pagination behavior, or what the response contains despite several include* flags changing the shape. For a 13-parameter tool with zero annotation coverage this is a substantive gap.

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?

Two sentences, front-loaded with the purpose, which is good. But 'Comprehensive tool' and the trailing 'etc.' are filler that dilute rather than inform, and the second sentence largely restates the first.

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?

With 13 optional parameters, no annotations, and no output schema, the description should at minimum clarify what is returned and how the include* flags affect payload size/behavior. The schema covers parameter semantics well, but return-shape and behavior remain implicit.

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 all 13 parameters are already documented in the schema, including pagination, filters, and the include* toggles. The description merely gestures at status/session-status/search/active-online filtering without adding syntax or interaction details, so the 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?

The description names a specific verb and resource ('retrieve WhatsApp devices') and lays out the scope of query scenarios it covers. It does not, however, distinguish itself from the sibling get_whatsapp_device_details, which an agent could easily confuse with this list-style tool.

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?

It enumerates usage scenarios (all devices, status/session-status filters, search, active/online only), which implies when to call it. But there is no explicit when-not guidance and no mention of the sibling get_whatsapp_device_details as the alternative for single-device lookups.

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.