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

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.

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 only declare readOnlyHint and idempotentHint, so the description carries the rest and does well: it discloses oldest-first ordering, the cursor/has_more pagination loop, and that until is exclusive. It does not state rate limits or scope/permission requirements, which keeps it short of 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.

Conciseness5/5

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

Three tight sentences, zero filler, and the scoping/ordering fact is front-loaded before pagination and filtering details. Every sentence adds a distinct operational instruction.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't restate return fields; it instead covers ordering, pagination, and time-window semantics. Nothing an agent needs to call this correctly is missing.

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 the schema already documents limit, since, until, account_id, and after_cursor in detail. The description's only parameter-level additions (until exclusivity, cursor paging) are already present in the schema, 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?

States a specific verb and resource — 'Read call history across your WhatsApp accounts' — plus the ordering (oldest first), so an agent immediately knows what it returns. It does not, however, disambiguate from the similarly named sibling wa_ai_list_calls, leaving the agent to infer the difference.

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 usage context: page with after_cursor, loop until has_more is false to export the entire history, and narrow the window with since/until. There is no explicit when-not or named alternative, but the operational guidance is clear.

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?