whatsmcp

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

TableJSON 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

TableJSON 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.

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"
+}

Changed2 schema fields changedOct 2, 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"
+}

Changed2 schema fields changedOct 2, 2026

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 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 and idempotentHint=false, so safety is covered. The description still adds real behavioral context beyond that: ascending chronological order, the cursor-termination contract ('keep going until has_more is false'), the exclusive nature of until, and the fact that each record carries answered status and duration.

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?

Three dense sentences with no filler; the scope and ordering come first, pagination and filtering follow. Every clause carries actionable information.

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, return-value detail is unnecessary, and the description covers ordering, pagination, filtering and exclusivity adequately. The one gap is disambiguation from wa_ai_list_calls, which an agent working in this 40-tool namespace would want.

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 the per-parameter formats (RFC3339, date shorthand, limit range) are already documented and the baseline would be 3. The description goes further by explaining the pagination workflow that spans after_cursor and the response's next_cursor/has_more, which is semantics the schema alone cannot express.

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 states a specific verb and resource — read call history across WhatsApp accounts — and adds ordering ('oldest first'), which a plain list name would not convey. It does not, however, distinguish itself from the sibling wa_ai_list_calls, so an agent cannot tell from the text alone which of the two call-listing tools is the right one.

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?

It gives concrete operational guidance: page with after_cursor by feeding back next_cursor until has_more is false, and narrow results with since/until. That is a clear usage pattern, but there is no explicit when-to-use or when-not-to-use statement relative to the sibling call-listing tools.

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?