WhatsMCP: MCP for WhatsApp

List Call History

wa_list_calls

Read-only

Read call history across your WhatsApp accounts, oldest first. Page with after_cursor: pass back the next_cursor you were given, and keep going until has_more is false to export the whole history. Each call says whether it was answered and how long it lasted. Narrow with since/until (until is exclusive).

Input Schema

Name	Required	Description
`limit`	No	how many to return, 1-200; defaults to 50
`since`	No	only calls at or after this time: RFC3339 with a zone (2026-10-01T09:00:00+03:00) or a date (2026-10-01 = midnight UTC); omit for no lower bound
`until`	No	only calls BEFORE this time — exclusive, so all of 1 October is since 2026-10-01 until 2026-10-02; same formats as since; omit for no upper bound
`account_id`	No	limit to one account; omit for every account you have
`after_cursor`	No	return calls after this cursor; omit to start from the oldest

Output Schema

Name	Required	Description
`calls`	Yes	calls in order, oldest first
`refusal`	No	present only when the request was declined
`has_more`	Yes	true when the page was full and more may be waiting
`next_cursor`	Yes	pass this as after_cursor next time; page until has_more is false to export everything

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / refusal / properties / candidates

Added value: +{
+  "description": "on an account_ambiguous refusal: the accounts to choose from — retry with one of these as account_id",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "account_id": {
+        "description": "the id to retry with as account_id",
+        "type": "string"
+      },
+      "name": {
+        "description": "the account's WhatsApp display name",
+        "type": "string"
+      },
+      "phone": {
+        "description": "the account's phone number, E.164",
+        "type": "string"
+      },
+      "status": {
+        "description": "whether the number works right now — live, connecting, or why not, as wa_list_accounts reports it",
+        "type": "string"
+      }
+    },
+    "required": [
+      "account_id"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

Changed3 schema fields changedOct 11, 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"
+}

Changed4 schema fields changedOct 5, 2026

addedInput schema / properties / since

Added value: +{
+  "description": "only calls at or after this time: RFC3339 with a zone (2026-10-01T09:00:00+03:00) or a date (2026-10-01 = midnight UTC); omit for no lower bound",
+  "type": "string"
+}

addedInput schema / properties / until

Added value: +{
+  "description": "only calls BEFORE this time — exclusive, so all of 1 October is since 2026-10-01 until 2026-10-02; same formats as since; omit for no upper bound",
+  "type": "string"
+}

addedOutput schema / properties / calls / items / properties / account_name

Added value: +{
+  "description": "the WhatsApp display name of that account",
+  "type": "string"
+}

addedOutput schema / properties / calls / items / properties / account_phone

Added value: +{
+  "description": "the phone number of your account that placed or received this call, E.164",
+  "type": "string"
+}

First observedSep 17, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already cover read-only safety, so the description's value is in disclosing ordering (oldest first), the termination condition for pagination, and that each call reports answered status and duration. It does not state rate limits or what happens if the cursor is stale, but the core loop behavior is well disclosed.

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

Conciseness5/5

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

Four short sentences, scope first, pagination mechanics next, filters last. No filler and no restatement of the title.

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 an output schema present and full parameter descriptions, the description only needs to cover workflow and ordering, which it does. The gap is sibling disambiguation against wa_ai_list_calls, the one thing an agent still has to guess.

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 100%, so baseline is 3; the description earns extra by explaining the cursor round-trip contract ('pass back the next_cursor you were given') and reiterating that until is exclusive, which is easy to get wrong even when documented in schema.

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?

Opens with a specific verb and resource — 'Read call history across your WhatsApp accounts' — and states the ordering (oldest first). It does not distinguish itself from the sibling wa_ai_list_calls, so an agent cannot tell from the description alone which of the two list-call tools applies.

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 concrete operational guidance: page with after_cursor, feed back next_cursor, continue until has_more is false, and narrow with since/until. It lacks a when-not-to-use or which-alternative clause (notably versus wa_ai_list_calls and wa_load_history).

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

All WhatsMCP: MCP for WhatsApp 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?