Meta Cloud API MCP Server

send_template_message

Send pre-approved WhatsApp template messages to recipients. Use approved templates to ensure message compliance and deliverability without manual approval.

Instructions

Send a pre-approved template message via WhatsApp. Templates must be created and approved before sending.

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

Input Schema

Name	Required	Description
`to`	Yes	Recipient phone number
`components`	No	Template components for variable substitution: [{type: "body", parameters: [{type: "text", text: "value"}]}]
`language_code`	Yes	Template language code (e.g. "en_US", "ko")
`template_name`	Yes	Approved template name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description bears the full burden. It adds the behavioral constraint that templates must be pre-approved. However, it does not disclose other traits such as delivery behavior, errors, or side effects beyond sending. This is arguably minimal viable transparency, but not rich enough for a score above 3.

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 a single sentence, 18 words, with the core purpose front-loaded. Every word contributes meaning; there is no wasted phrasing. This is exemplary conciseness.

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 sending tool with moderate complexity, the description covers the essential context: what it sends, via which channel, and the prerequisite of approval. There is no output schema, but the absence of return-value documentation is not a significant gap given the straightforward nature of the tool. It is complete enough for correct selection and invocation.

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?

Input schema coverage is 100%, with each parameter having a description. The tool description itself does not add parameter semantics beyond what the schema already provides. Baseline 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?

The description uses a specific verb 'Send' with a clear resource 'pre-approved template message via WhatsApp'. It distinguishes from sibling send tools like send_text_message and send_image_message by emphasizing 'template' and 'pre-approved'. The requirement of creation/approval adds further differentiation.

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?

The description gives clear context: templates must be created and approved before sending, implying use of template management tools first. It does not explicitly name alternatives or exclusions, but the prerequisite is a strong usage signal. This qualifies as clear context without exclusions.

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