Skip to main content
Glama
Maheidem

WAHA WhatsApp MCP Server

by Maheidem

Search WhatsApp Messages

whatsapp_search_messages
Read-onlyIdempotent

Search your entire WhatsApp history for specific messages using text, date range, sender, and type filters.

Instructions

Search across all WhatsApp message history. Supports full-text search, date ranges, sender filtering, and message type filtering.

Args:

  • search: Text to search for (case insensitive, supports Portuguese/unicode)

  • contactId: Scope search to one contact (phone digits or "*@g.us") (optional)

  • sender: Filter by sender name or JID (optional)

  • since: ISO date string — messages after this date (optional)

  • until: ISO date string — messages before this date (optional)

  • type: Message type filter: chat, image, album, e2e_notification (optional)

  • fromMe: Filter sent (true) or received (false) messages (optional)

  • limit: Results per page (1-100, default 20)

  • offset: Pagination offset (default 0)

Returns:

  • messages: Array with id, chatJid, senderName, body, timestamp, messageType, fromMe

  • total: Total matching messages

  • has_more: Whether more results exist

Note: sender_name may be null for some messages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
searchYesText to search for (case insensitive)
contactIdNoScope search to one contact: phone digits (person) or "*@g.us" (group). Optional.
senderNoFilter by sender name or JID (optional)
sinceNoISO date string — only messages after this date (optional)
untilNoISO date string — only messages before this date (optional)
typeNoMessage type filter: chat, image, album, e2e_notification (optional)
fromMeNoFilter: true = sent, false = received (optional)
limitNoResults per page (1-100, default 20)
offsetNoPagination offset (default 0)
Behavior4/5

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

Annotations declare readOnlyHint=true and idempotentHint=true. Description adds case-insensitive search, Portuguese/unicode support, and notes that sender_name may be null. This provides value 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 summary, Args, and Returns. Front-loaded with key purpose. Slightly lengthy but clear.

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 high parameter count (9) and no output schema, description fully explains each parameter, return structure, and behavioral traits (case-insensitivity, null sender_name). Complete for agent use.

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 100%, so baseline is 3. Description repeats schema parameter descriptions almost verbatim, adding only case-insensitivity note and return format. Minimal added value.

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 specify the tool searches WhatsApp messages with full-text, date, sender, and type filters. It distinguishes from siblings like whatsapp_list_chats and whatsapp_read_messages.

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?

No explicit when-to-use or when-not-to-use instructions. Usage is implied through description, but no alternatives are mentioned.

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