Skip to main content
Glama
whatsapp-cloud-mcp

whatsapp-cloud-mcp

Send WhatsApp template message

send_template_message

Start or re-open a WhatsApp conversation by sending a pre-approved message template with body, header, and button parameters to a recipient phone number.

Instructions

Send a pre-approved WhatsApp message template. Templates are REQUIRED to start a conversation (or to re-engage a user after the 24-hour customer-service window has closed). Use body_parameters for simple {{1}},{{2}} placeholders, or components for advanced header/button parameters. Discover templates with list_message_templates.

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>"
    },
    "name": "send_template_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient phone number, ideally E.164 (e.g. +971501234567)
componentsNoFull components array (header/body/button parameters) for advanced templates
language_codeNoTemplate language code, e.g. en_US or aren_US
template_nameYesApproved template name, e.g. hello_world
body_parametersNoShortcut: values for {{1}}, {{2}}… in the template body

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations declare openWorldHint=true and destructiveHint=false, so the safety profile is already covered; the description adds real context beyond that with the pre-approval requirement and the 24-hour window constraint that governs whether this call is legal at all. Return shape, delivery confirmation, and failure modes for unapproved templates are not mentioned.

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, each earning its place: purpose, the hard business constraint, then parameter strategy and discovery. The window rule and the send action are front-loaded with zero filler.

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?

For a 5-parameter outbound-messaging tool with no output schema, the description covers what to send, when it is permitted, and how to fill parameters. Gaps are minor: nothing about idempotency, rate limits, or what happens when a template name or language code does not match an approved template.

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 schema already documents every parameter including the components union types. The description does add a useful decision rule between the two overlapping parameters (body_parameters for simple {{1}},{{2}} placeholders vs components for header/button parameters), which lifts it above pure repetition, but no format examples or constraints are added.

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?

"Send a pre-approved WhatsApp message template" gives a specific verb and resource, and the 24-hour-window sentence implicitly separates it from freeform senders like send_text_message. It does not name the freeform alternative explicitly, so the distinction must be inferred from the window rule rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use is given: starting a conversation or re-engaging after the customer-service window closes. It also routes to list_message_templates for discovery. It stops short of stating when NOT to use it (e.g. replying inside the 24-hour window, where send_text_message would apply).

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