Skip to main content
Glama
wazap-mcp

wazap-mcp

by razvangirgiz

List WhatsApp chats

list_chats
Read-onlyIdempotent

Lists WhatsApp conversations by recent activity, returning chat IDs, names, unread counts, last messages, and status flags; filter by unread, groups, individuals, archived, or tag 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.

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
tagNoOnly chats with people filed under this tag
limitNo
cursorNonext_cursor of the previous page; same filter
filterNo"all" leaves out archivedall
account_idNo
include_picturesNoAdd picture_url, each chat's profile photo (links expire)

Output Schema

NameRequiredDescriptionDefault
tagNo
syncYes
chatsYes
countYes
filterYes
account_idYes
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.7.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque next_cursor from the preceding page; keep the same filter"New value: +"next_cursor of the previous page; same filter"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / properties / chats / items / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / chats / items / properties / last_message / anyOf
      Previous value: -[
      -  {
      -    "additionalProperties": true,
      -    "properties": {
      -      "private": {
      -        "const": true,
      -        "description": "Tagged #private: no words",
      -        "type": "boolean"
      -      }
      -    },
      -    "type": "object"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "additionalProperties": {},
      +    "properties": {
      +      "private": {
      +        "const": true,
      +        "description": "Tagged #private: no words",
      +        "type": "boolean"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Changed3 schema fields changedv1.6.0
    • 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"
      +}
  3. Changed2 schema fields changedv1.4.2
    • 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"
      +  ]
      +}
  4. Changed1 schema field changedv1.4.0
    • addedInput schema / properties / include_pictures
      Added value: +{
      +  "default": false,
      +  "description": "Add picture_url, each chat's profile photo (links expire)",
      +  "type": "boolean"
      +}
  5. Changed4 schema fields changedv1.0.3
    • 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"
      +}
  6. Changed1 schema field changedv0.15.0
    • 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"
      +}
  7. First observedv0.9.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds the ordering guarantee (recency) and that each chat exposes archive/pin/mute/left state, but much of the field list duplicates the existing output schema. Pagination behavior via cursor is left entirely to the schema.

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 the resource and ordering, with the actionable hint last. Slight waste in enumerating return fields that the output schema already specifies, but nothing is confusing or padded.

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?

Annotations and an output schema cover safety and return shape, so the description only needs to place the tool among alternatives and clarify inputs. It does the first weakly and the second not at all, leaving limit/account_id semantics undocumented for a six-parameter 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 coverage is 67%, with the tag, cursor and filter enums documented, but limit and account_id carry no schema description and the tool description adds nothing about them. The fields named in the description (chat_id, name, unread count, etc.) are return values, not inputs, so no input meaning is contributed.

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 identifies the resource (conversations/chats) and its ordering ('most recently active first'), plus what each entry carries, so an agent knows this is a chat enumeration tool. It stops short of naming a sibling to contrast with (e.g. search, manage_chat), so differentiation is inferred rather than stated.

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 a single implied use case, which is genuinely helpful as a routing hint. It offers no when-not guidance, no mention of how it differs from search or list_contacts, and no note that filtered/paginated retrieval is available for large accounts.

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