Skip to main content
Glama
WhatsApp Groups MCP

WhatsApp Groups MCP

by mlteam-ai

search_messages

Find messages by case-insensitive substring in allowed WhatsApp groups, optionally filter by group or since date, with newest results first.

Instructions

Search message text (case-insensitive substring) in allowed groups.

group_jid: limit to one group. since: ISO date like 2026-11-01. Newest first.

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": {
      "query": "<query>"
    },
    "name": "search_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
sinceNo
group_jidNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose two real traits — case-insensitive substring matching and newest-first ordering, plus a permission scope ('allowed groups') — but it says nothing about how 'limit' behaves (truncation vs pagination), whether results are capped, or any rate/permission failure behavior for a search across potentially many groups.

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 short blocks: one front-loaded sentence stating the operation and matching rule, then a compact parameter-hint line. Every clause carries information and nothing is padded.

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?

An output schema exists, so return values need not be explained, and ordering is covered. However, for a four-parameter tool with zero schema documentation, the silent 'limit' parameter and the unstated default behavior when group_jid is omitted leave real gaps an agent would need to guess at.

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?

With 0% schema description coverage, the schema offers only titles, so the description must compensate. It adds genuine meaning for query (substring, case-insensitive), since (ISO date with a concrete example), and group_jid (restricts to one group), but 'limit' is left completely opaque — no meaning, no maximum, only the schema's default of 50.

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 names a specific verb and resource and pins down the matching semantics: 'Search message text (case-insensitive substring) in allowed groups.' That is enough for an agent to distinguish it from get_messages or list_groups by role, though it never explicitly contrasts itself with those siblings.

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?

'in allowed groups' and 'group_jid: limit to one group' imply default scope and an optional narrowing, and 'Newest first' hints at result ordering. There is no explicit when-to-use guidance and no statement of when to prefer get_messages instead, so usage must be inferred.

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