whatsapp-mcp-server

whatsapp_send_template

Send an approved WhatsApp template to a recipient, replacing header, body, and button placeholders with dynamic values.

Instructions

Send an approved WhatsApp message template. Templates are pre-approved messages used for business-initiated conversations. Supports header, body, and button components with dynamic variable substitution.

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>",
      "template_name": "<template_name>",
      "language_code": "<language_code>"
    },
    "name": "whatsapp_send_template"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	Recipient phone number in E.164 format, e.g. +15551234567
`components`	No	Template components with dynamic values. Include header, body, and/or button components as needed.
`language_code`	Yes	Language code for the template, e.g. en_US, pt_BR, es, fr
`template_name`	Yes	Name of the approved template to send
`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

Behavior3/5

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

No annotations provided, so description carries full burden. It explains support for header, body, button components and dynamic substitution, but omits important behavioral traits like rate limits, authentication, or WhatsApp policy constraints (e.g., 24-hour window, opt-in).

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?

Three sentences that are directly to the point: action, purpose, and capabilities. No redundant 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?

Covers the core purpose and component usage, but lacks details on return value, error handling, and prerequisites (e.g., template approval, account setup). For a tool with no output schema and no annotations, more context is needed for safe agent usage.

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% with descriptions for all parameters. The description adds context about component types and dynamic variables but does not significantly enhance understanding beyond the schema. Baseline score applies.

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 'Send an approved WhatsApp message template', distinguishing it from other send tools like whatsapp_send_text by specifying pre-approved templates for business-initiated conversations. The verb-resource combination 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?

No explicit guidance on when to use or not use this tool versus alternatives. Mentions 'business-initiated conversations' but does not compare to other send methods or outline prerequisites like requiring an approved template.

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

Deploy Server