whatsapp-mcp

list_chats

Retrieve WhatsApp chats—people and groups—most recent first, including phone numbers and unread counts, and filter to only those with unread messages.

Instructions

List WhatsApp chats (people and groups), most recent first, with phone numbers and unread counts. unread_only: only chats with unread messages.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_chats"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`unread_only`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does supply useful behavior: result ordering ('most recent first') and returned fields ('phone numbers and unread counts'). It omits pagination behavior, any default or maximum for the result set, and whether account authentication is assumed.

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?

Two short sentences, front-loaded with the core verb and resource, then the one non-obvious parameter note. Nothing redundant.

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

Completeness3/5

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

No output schema exists, so the description must convey return shape; it does partially via the mention of phone numbers and unread counts, but leaves limit semantics and pagination uncovered, which matters for a listing 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 0%, and the description meaningfully defines one of the two parameters ('unread_only: only chats with unread messages'). The 'limit' parameter is left entirely unexplained — no default, no maximum, no statement of what happens when it is omitted.

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 concrete verb and resource ('List WhatsApp chats (people and groups)') and adds scope and ordering ('most recent first'), which lets an agent distinguish it from list_messages without opening either schema. It stops short of naming that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the phrase 'List WhatsApp chats' and the unread_only note; there is no explicit when-to-use or when-not rule, and no pointer to search_contacts/search_messages for lookup-style needs.

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

Deploy Server