Skip to main content
Glama

whatsapp_numbers_read

Read-onlyIdempotent

Read details of the WhatsApp numbers connected to an agent. For a quick "is it connected" check use get_agent_channels; for reply rules use get_whatsapp_ai_rules. Actions: list — all numbers of the agent with status, mode and settings | details — live info from Meta: display name, quality rating, messaging limit tier, verification Needs: phoneId. | analytics — WhatsApp conversation and message analytics for the agent | voice_status — re-check with Meta whether WhatsApp voice calling is enabled on the number Needs: phoneId.

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": {
      "action": "<action>",
      "agentId": "<agentId>"
    },
    "name": "whatsapp_numbers_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNocompact (default) = light mode: long text is cut and bulky blobs are replaced by a size marker. full = complete API response.
actionYes
agentIdYes
phoneIdNoMeta WhatsApp phone number ID (from get_agent_channels), not the phone number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: 'details' and 'voice_status' are live fetches against Meta (freshness/latency implication), and it tells the agent which actions require phoneId. No mention of failure modes or rate limits, so not a 5.

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 statement and the sibling routing are front-loaded in the first two sentences, before the pipe-delimited action breakdown. The density is high but every clause carries information; minor redundancy in repeating 'Needs: phoneId.' twice is the only waste.

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?

With no output schema, the description does the work of hinting return content per action (status/mode/settings; display name, quality rating, messaging limit tier, verification; conversation and message analytics). That is enough for an agent to pick the right action; it stops short of describing shape or pagination for analytics.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% — 'mode' and 'phoneId' are documented in the schema, while 'action' and 'agentId' are not. The description compensates by defining what each of the four action values returns and by tying phoneId to the two actions that need it, which is the key semantic the schema omits. 'agentId' remains unelaborated but is self-evident.

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 opening sentence gives a specific verb and resource ('Read details of the WhatsApp numbers connected to an agent'), and the action list enumerates the four distinct modes of reading. It explicitly names the siblings it is not (get_agent_channels, get_whatsapp_ai_rules), so the agent can distinguish it 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?

It routes the agent away from this tool for the 'is it connected' check and for reply rules, naming the exact alternatives. Each action is scoped (list = all numbers of the agent, details = live Meta data, analytics = conversation metrics, voice_status = re-check with Meta) with per-action prerequisites stated as 'Needs: phoneId.'

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.

Resources