Skip to main content
Glama
WhatsApp MCP Server

WhatsApp MCP Server

list_chats

Retrieve recent WhatsApp one-to-one and group chats with contact, unread count, timestamp, preview, archive and pin status. Filter by search, unread status, and pagination.

Instructions

List recent 1:1 and group chat sessions from WhatsApp's local storage. Includes contact name, JID, unread count, last message date, last message text preview, archived status, and pinned status.

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

NameRequiredDescriptionDefault
limitNoMaximum number of chats to return (default 50, max 200).
offsetNoNumber of records to skip for pagination.
searchNoOptional filter matching contact name, group title, or phone number / JID.
unread_onlyNoIf true, return only chats with unread messages.
include_archivedNoWhether to include archived chats.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden; it does disclose the read source (local storage) and exactly which fields come back, which is real behavioral content. It omits ordering guarantees, whether results are truncated by the limit silently, and any failure mode when WhatsApp storage is unavailable or locked.

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?

Two sentences, front-loaded with purpose followed by return fields, with no filler. The field enumeration is dense but each item is informative for an agent deciding whether this tool answers its question.

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?

For a read-only list tool with no annotations and no output schema, the description covers what is returned but not ordering, pagination interaction, or edge cases. It is adequate to call the tool but thin on the behavioral guarantees an agent might rely on.

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 adds meaning by framing the result set (

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 (list) and resource (1:1 and group chat sessions) plus the data source (WhatsApp local storage), and enumerates the returned fields. This distinguishes it from list_messages and get_chat, which operate on message content or a single chat.

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?

The word 'recent' and the field list imply this is the discovery/listing entry point before calling get_chat or list_messages, but no alternative is named and there is no explicit when-not-to-use guidance. Usage is inferable rather than stated.

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