whatsmcp

Get an AI Voice-Agent Call

wa_ai_call_get

Read-only

Read an AI call started with wa_ai_call_start: status (dialing, in_progress, done, failed, no_answer, busy), and once it has ended the summary, whether the agent judged it successful, the data it collected, the transcript, and a recording_url valid for one hour.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`call_ref`	Yes	from wa_ai_call_start

Output Schema

TableJSON Schema

Name	Required	Description
`call`	No	the call; transcript, summary and data fill in once it has ended
`next`	No	what to do next
`refusal`	No	present only when the request was declined
`recording_url`	No	MP3 of the call, valid for one hour; present once recording_state is saved

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 14, 2026

addedOutput schema / properties / refusal / properties / account_status

Added value: +{
+  "description": "when the number is not working: its status — starting, not_running, whatsapp_down, suspended, pairing, unlinked or locked",
+  "type": "string"
+}

addedOutput schema / properties / refusal / properties / account_status_reason

Added value: +{
+  "description": "the detail of account_status, e.g. no_egress, stopped, no_plan",
+  "type": "string"
+}

addedOutput schema / properties / refusal / properties / since

Added value: +{
+  "description": "when the number stopped working, RFC3339, when known",
+  "type": "string"
+}

Changed3 schema fields changedSep 28, 2026

addedOutput schema / properties / call / properties / direction
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / call / properties / from
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / properties / call / required

Previous value: -[
-  "call_ref",
-  "status",
-  "preset",
-  "account_id",
-  "to",
-  "created_at",
-  "recording_state"
-]New value: +[
+  "call_ref",
+  "direction",
+  "status",
+  "preset",
+  "account_id",
+  "to",
+  "created_at",
+  "recording_state"
+]

First observedSep 27, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds genuinely new behavioral detail beyond them: the full status lifecycle (dialing, in_progress, done, failed, no_answer, busy), the condition that summary/transcript/data appear only 'once it has ended', and that recording_url expires after one hour. The one-hour expiry is a real operational constraint an agent must plan around.

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?

A single dense sentence, front-loaded with the action and its prerequisite, with the return contents listed compactly. The long comma-separated list of fields makes it slightly scannable-poor, but there is no filler text.

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?

An output schema exists, so the description is not obligated to enumerate return values, yet it usefully flags when those values are populated and the recording URL's lifetime. What remains unaddressed is error/not-found behavior for an invalid call_ref, which would help for a status-polling tool.

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 the single parameter already carries the note 'from wa_ai_call_start'; the description only restates that provenance. Baseline 3 is correct since the schema does the heavy lifting and no extra syntax or format guidance is added.

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+resource ('Read an AI call started with wa_ai_call_start') and enumerates exactly what comes back (status, summary, success judgement, collected data, transcript, recording_url). This clearly separates it from wa_ai_list_calls (enumerate) and wa_ai_call_start (create).

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?

Explicitly ties the tool to its prerequisite ('an AI call started with wa_ai_call_start') and implies polling via the status field, giving clear context for when to call it. It stops short of naming alternatives such as wa_ai_list_calls for bulk retrieval, so it is clear but not fully routed.

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

All whatsmcp 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.

Resources

Need Help?