Skip to main content
Glama
wati-io

WhatsApp MCP Server

by wati-io

list_contacts

Retrieve WhatsApp contacts with pagination support by specifying page size and page number to navigate results.

Instructions

List WhatsApp contacts with pagination.

Args:
    page_size: Number of contacts per page (max 100, default 20)
    page_number: Page number, 1-based (default 1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_sizeNo
page_numberNo
Behavior3/5

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

No annotations exist, so the description must cover behavior. It discloses pagination parameters and constraints (max page_size 100), but does not mention ordering, total count, or any side effects. It is adequate but not comprehensive.

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?

The description is concise: one sentence followed by clear parameter docs. It is front-loaded with the main purpose and wastes no words.

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?

Given no output schema, the description does not explain what the response contains (e.g., contact objects). For a simple list tool, this is a moderate gap.

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?

With 0% schema description coverage, the description adds significant value by providing defaults and constraints (page_size max 100). This compensates for the bare schema.

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?

The description clearly states the tool lists WhatsApp contacts with pagination, using a specific verb and resource. It distinguishes from siblings like search_contacts (which likely filters) and get_contact (single contact).

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool vs alternatives like search_contacts. No when-not-to-use or explicit context is given.

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/wati-io/wati-mcp-server'

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