whatsapp-mcp-server

whatsapp_send_document

Deliver documents such as PDF, Word, and Excel to WhatsApp phone numbers using a publicly accessible URL. Optionally add a caption and filename.

Instructions

Send a document or file to a WhatsApp phone number. Supports PDF, Word, Excel, and other common formats.

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": {
      "to": "<to>",
      "document_url": "<document_url>"
    },
    "name": "whatsapp_send_document"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Phone number in E.164 format, e.g. +15551234567
`caption`	No	Optional caption
`filename`	No	Filename shown to recipient
`document_url`	Yes	Publicly accessible URL of the document
`reply_to_message_id`	No	Message ID to reply to

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Jun 26, 2026

TDQS

A3.5/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the action and supported formats, but lacks details on potential issues like URL validity, size limits, internet requirements, or error handling.

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?

The description is minimal and efficient: two sentences with no wasted words. Every sentence serves a purpose—stating the action and specifying supported formats.

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?

Given the absence of an output schema, the description does not explain return values or what happens after sending. It adequately covers the basic purpose and supported formats, but lacks details on prerequisites, error conditions, or status outcomes.

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 the baseline is 3. The description adds context about supported formats for document_url, but does not provide further meaning beyond what the schema already offers for other parameters.

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?

The description clearly states the verb 'Send' and the resource 'document or file to a WhatsApp phone number', and lists supported formats (PDF, Word, Excel), which distinguishes it from sibling tools like whatsapp_send_image or whatsapp_send_video.

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?

The description implies usage for sending documents but provides no explicit guidance on when to use this tool versus alternatives like whatsapp_send_image or whatsapp_send_text, nor any conditions for avoiding it.

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

Deploy Server