Skip to main content
Glama
WhatsApp Groups MCP

WhatsApp Groups MCP

by mlteam-ai

get_messages

Read a WhatsApp group's messages in chronological order, optionally from a specified ISO date, to retrieve recent chat history for answering questions.

Instructions

Read a group's messages in time order. since: ISO date; default returns the latest limit 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": {
      "group_jid": "<group_jid>"
    },
    "name": "get_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNo
group_jidYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses ordering and the default window (latest `limit` messages), which is genuinely useful, but says nothing about read-only safety, permissions needed to read a group, pagination, or what happens when `since` and `limit` conflict.

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 sentences, zero filler, with the core behavior front-loaded and the parameter hint following. Nothing could be cut without losing information.

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 described, and the default-window behavior is covered. For a three-parameter tool with zero schema documentation, though, the interaction between `since` and `limit` and the identity of `group_jid` remain unexplained.

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 0%, so the description must compensate and partially does: `since` is defined as an ISO date and `limit` is given meaning through 'latest `limit` messages'. The required `group_jid` gets no explanation of format or source, leaving a real gap.

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?

States a specific verb and resource ('Read a group's messages') plus the ordering guarantee ('in time order'), which is more than a restatement of the name. It does not distinguish itself from the sibling search_messages, so an agent cannot tell from this text alone which one to pick.

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 when-to-use guidance and no exclusions; the sibling search_messages is never mentioned. The only implied routing cue is the word 'Read' versus searching, which the agent must infer.

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