Skip to main content
Glama
Sign In
wwebjs-mcp

wwebjs-mcp

by victor-halla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

client_searchMessages

Search WhatsApp messages within a session using a query string and pagination options. Retrieve matching messages to find specific content.

Instructions

[Client] Search for messages

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sessionId": "<sessionId>"
    },
    "name": "client_searchMessages"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSearch string
optionsNoSearch options
sessionIdYesUnique identifier for the session (alphanumeric and - allowed)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description must carry the full burden of behavioral disclosure, but it only says 'Search for messages'. It does not state whether the operation is read-only, whether pagination or limits apply, or how sessionId scopes the search.

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?

The description is extremely concise and front-loaded with the core purpose, containing no filler. However, it is more of a fragment than a well-structured description, and the lack of detail is not compensated by any structural elements.

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

Completeness2/5

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

Given no annotations, no output schema, and a nested options object, the one-line description is insufficient for confident invocation. Missing return format, pagination behavior, and usage context force the agent to make significant assumptions.

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?

The input schema provides descriptions for all three parameters, so schema coverage is 100%, earning the baseline 3. The description adds no parameter-level meaning, and the 'options' description remains vague, but this is not a gap beyond what the schema already provides.

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 uses the specific verb 'Search' and resource 'messages', clearly indicating the tool's function. It distinguishes from sibling 'client_searchChannels' by targeting messages, though it lacks detail on scope or filtering behavior.

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?

No guidance is provided on when to use this tool versus alternatives like 'client_searchChannels' or 'chat_fetchMessages'. The description does not mention required session context, exclusions, or how this search differs from other message-fetching tools.

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