wazap-mcp

List WhatsApp chats

list_chats

Read-onlyIdempotent

Retrieve WhatsApp conversations, most recently active first, with unread counts, last message, and archived, pinned, muted or left status. Use it to find a chat_id.

Instructions

Conversations, most recently active first: chat_id, name, type, unread count, last message, and whether archived, pinned, muted or left. Use it to find a chat_id.

Input Schema

Name	Required	Description	Default
`tag`	No	Only chats with people filed under this tag
`limit`	No
`cursor`	No	Opaque next_cursor from the preceding page; keep the same filter
`filter`	No	"all" leaves out archived	all
`account_id`	No
`include_pictures`	No	Add picture_url, each chat's profile photo (links expire)

Output Schema

Name	Required	Description	Default
`tag`	No
`sync`	Yes
`chats`	Yes
`count`	Yes
`filter`	Yes
`account_id`	Yes
`next_cursor`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.6.0Oct 22, 2026

removedInput schema / properties / account_id / description
```
Removed value: -"Account id"
```

addedInput schema / properties / tag

Added value: +{
+  "description": "Only chats with people filed under this tag",
+  "maxLength": 40,
+  "minLength": 1,
+  "type": "string"
+}

addedOutput schema / properties / tag
```
Added value: +{
+  "type": "string"
+}
```

Changed2 schema fields changedv1.4.2Oct 18, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "Opaque next_cursor from the preceding page; keep the same filter",
+  "maxLength": 512,
+  "type": "string"
+}

addedOutput schema / properties / next_cursor

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed1 schema field changedv1.4.0Oct 15, 2026

addedInput schema / properties / include_pictures

Added value: +{
+  "default": false,
+  "description": "Add picture_url, each chat's profile photo (links expire)",
+  "type": "boolean"
+}

Changed4 schema fields changedv1.0.3Sep 23, 2026

changedInput schema / properties / account_id / description

Previous value: -"Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account."New value: +"Account id"

changedInput schema / properties / filter / description

Previous value: -"Which chats to list; \"all\" (default) excludes archived ones"New value: +"\"all\" leaves out archived"

removedInput schema / properties / limit / description
```
Removed value: -"Maximum number of chats (1-100)"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "account_id": {
+      "type": "string"
+    },
+    "chats": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "chat_id": {
+            "type": "string"
+          },
+          "last_message": {
+            "anyOf": [
+              {
+                "additionalProperties": true,
+                "properties": {
+                  "private": {
+                    "const": true,
+                    "description": "Tagged #private: no words",
+                    "type": "boolean"
+                  }
+                },
+                "type": "object"
+              },
+              {
+                "type": "null"
+              }
+            ]
+          },
+          "name": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          },
+          "unread_count": {
+            "type": "number"
+          }
+        },
+        "required": [
+          "chat_id",
+          "name",
+          "type",
+          "unread_count"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "count": {
+      "type": "number"
+    },
+    "filter": {
+      "type": "string"
+    },
+    "sync": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "filter",
+    "count",
+    "chats",
+    "sync",
+    "account_id"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv0.15.0Sep 12, 2026

addedInput schema / properties / account_id

Added value: +{
+  "description": "Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.",
+  "minLength": 1,
+  "type": "string"
+}

First observedv0.9.3Aug 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description only needed to add context beyond that. It does: result ordering, the set of surfaced fields, and the presence of archived/pinned/muted/left flags. It says nothing about page size behavior or what happens when the account has no chats, so it stops 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.

Conciseness4/5

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

Two tight sentences, front-loaded with what comes back and ordering, ending with the actionable purpose. The field enumeration is somewhat redundant given an output schema exists, but it earns its place by letting an agent judge suitability at a glance.

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?

Return values needn't be explained since an output schema exists, and the description covers ordering and flags. Gaps remain around pagination expectations (limit/cursor are only sketched in the schema), the required account_id, and how this differs from search or list_contacts — for a 6-parameter tool that's the minimum viable level.

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 coverage sits at 67% and the description mentions no parameters at all — tag, filter, cursor, and include_pictures are documented only in the schema, while limit and account_id are undocumented in both places. With the majority of parameters covered by structured fields, the baseline of 3 is right, but the description adds no semantic lift.

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 the specific resource (chats/conversations), the ordering (most recently active first), and the fields returned, plus the concrete downstream purpose (find a chat_id). It does not distinguish itself from siblings like search or find_contact, which is the only thing keeping it from a 5.

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?

"Use it to find a chat_id" gives one concrete use case, which implies this is the discovery/listing entry point. But there are no exclusions or comparisons to alternatives such as search or list_contacts, so the agent must infer when this beats a search.

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