Skip to main content
Glama
razvangirgiz

wazap-mcp

by razvangirgiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Search WhatsApp messages

search_messages
Read-onlyIdempotent

Find locally synced WhatsApp messages by case-insensitive text across all chats or one chat, with sender, date, and limit filters. Only messages already synced to this device are searchable.

Instructions

Case-insensitive text search over the messages wazap holds locally — all chats, or one chat. It cannot reach messages the phone never synced to this device.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fromNoOnly messages this person sent: "me", a contact id or a phone number
limitNoMaximum number of results (1-50)
queryYesText to search for
sinceNoOnly messages from this moment on: a date ("2026-09-01") or an ISO timestamp
untilNoOnly messages up to this moment: a date or an ISO timestamp
chat_idNoRestrict the search to this chat
account_idNoRegistry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields 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"
+}
    • addedInput schema / properties / from
      Added value: +{
+  "description": "Only messages this person sent: \"me\", a contact id or a phone number",
+  "minLength": 1,
+  "type": "string"
+}
    • addedInput schema / properties / since
      Added value: +{
+  "description": "Only messages from this moment on: a date (\"2026-09-01\") or an ISO timestamp",
+  "minLength": 4,
+  "type": "string"
+}
    • addedInput schema / properties / until
      Added value: +{
+  "description": "Only messages up to this moment: a date or an ISO timestamp",
+  "minLength": 4,
+  "type": "string"
+}
  2. First observedv0.9.3

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world. The description adds a genuinely useful non-obvious constraint — the local-sync data boundary — that annotations cannot convey. It does not describe result ordering or pagination behavior.

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?

Two tight sentences with the core capability front-loaded and the limitation following immediately. Every clause earns its place; no restatement of the name or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only search tool with a rich, fully documented 7-parameter schema and no output schema, the description covers purpose, scope, and the key data-boundary caveat. It omits anything about result volume defaults/ordering, but those are secondary.

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 description coverage is 100%, so all seven parameters (from, limit, query, since, until, chat_id, account_id) are already documented in the schema. The description's 'all chats, or one chat' allusion to chat_id adds nothing beyond the schema. Baseline 3 applies.

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?

States a specific verb (case-insensitive text search) and resource (messages), plus scope (all chats or one chat). This distinguishes it from read_messages and get_recent_messages, which retrieve rather than search.

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?

Gives clear context for use (local search over all chats or one chat) and an explicit boundary — it cannot reach messages never synced to the device. It does not name sibling alternatives (e.g., read_messages for a whole thread), so routing is implied rather than spelled out.

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

Deploy Server

Other Tools