Skip to main content
Glama
Maheidem

WAHA WhatsApp MCP Server

by Maheidem

List WhatsApp Contacts (people + groups)

whatsapp_list_contacts
Read-onlyIdempotent

Lists WhatsApp contacts (people and groups) with IDs, names, and activity stats. Use returned IDs as contactId for sending messages or reading chats.

Instructions

Unified address book — lists people you DM and groups you're in.

Use the returned 'id' as contactId in any chat-targeting tool (send_text, read_messages, etc.):

  • Person: id = phone digits (universal — survives @c.us↔@lid flips)

  • Group: id = group JID (e.g. "120363...@g.us")

Args:

  • kind: "person" | "group" | "all" (default "all")

  • search: Filter by name or id (optional)

  • limit: Maximum rows to return (1-100, default 20)

  • offset: Pagination offset for the persons section (default 0)

Returns array of contacts with:

  • kind: "person" | "group"

  • id: phone digits or group JID — pass to other tools

  • name: display name (Google Contact name → push name → phone/jid fallback)

  • messageCount, lastMessageAt: activity stats

  • For persons: pushName, googleName, email, organization

  • For groups: memberCount

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoFilter by contact type (default 'all')all
searchNoFilter by name or id (optional)
limitNoMaximum rows to return (1-100, default 20)
offsetNoPagination offset (default 0)
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent. Description adds behavioral details about ID formats, name resolution fallback, and pagination, which is valuable beyond annotations.

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?

Description is well-structured with Args and Returns sections. It is concise but thorough, though slightly verbose in explaining ID formats and fallbacks.

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?

Given 4 parameters, no output schema, and strong annotations, the description fully explains return structure, ID usage, pagination, and filtering options. No gaps.

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 has 100% description coverage, so description adds only marginal value for parameters. It explains the kind enum and output context, but the schema already provides clear parameter descriptions.

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?

Title and description clearly state the tool lists WhatsApp contacts (people and groups). Description distinguishes from siblings like whatsapp_list_chats and whatsapp_get_contact. Uses specific verbs and resource types.

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?

Description explicitly explains how to use returned IDs for chat-targeting tools, but doesn't state when not to use or alternatives. Still provides clear usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Maheidem/waha-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server