whatsapp-mcp-server

whatsapp_get_conversation

Get message history for a specific WhatsApp conversation by providing the phone number. Optionally set a limit on the number of messages returned.

Instructions

Get the message history for a conversation with a specific phone number. Requires webhook server.

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": {
      "phone_number": "<phone_number>"
    },
    "name": "whatsapp_get_conversation"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of messages to return (default 50)
`phone_number`	Yes	Phone number in E.164 format, e.g. +15551234567

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 26, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations, so description bears full burden. It discloses the webhook requirement but doesn't explain pagination, error cases, or that it returns a list of messages. Adequate but not thorough.

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 sentences, front-loaded with purpose. No wasted words. Highly concise.

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?

Simple tool with well-documented parameters. Missing details on pagination and return structure, but overall adequate for its simplicity.

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 the description adds no additional meaning beyond the schema. Baseline score of 3 is appropriate.

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?

Clearly states it gets message history for a specific phone number, which distinguishes it from list_conversations (summary) and send tools. Verb+resource is specific.

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?

Only mentions a prerequisite (webhook server). Does not provide guidance on when to use vs alternatives (e.g., list_conversations), nor when not to use.

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

Deploy Server