whatsmcp

Create WhatsApp Business Template

wa_create_template

Submit a new WhatsApp Business message template for Meta's review on one of your Business (Cloud API) numbers. Meta reviews it (usually minutes, sometimes longer); it can be sent with wa_send_message's template option only once wa_list_templates shows it APPROVED. Categories: MARKETING or UTILITY. Number body variables {{1}}, {{2}}, … in order and give one body_examples value per variable. Templates apply only to Business numbers.

Input Schema

TableJSON Schema

Name	Required	Description
`body`	Yes	the message text, at most 1024 characters; variables are {{1}}, {{2}}, … numbered in order
`name`	Yes	lowercase letters, digits and underscores, e.g. order_update
`footer`	No	optional footer, at most 60 characters, no variables
`header`	No	optional text header, at most 60 characters and one {{1}} variable
`buttons`	No	optional buttons: at most 10, of which at most 2 URL and 1 PHONE_NUMBER
`category`	Yes	MARKETING or UTILITY
`language`	No	language code such as en_US (the default), en or pt_BR
`account_id`	Yes	the Business (Cloud API) account to create the template on, as returned by wa_list_accounts
`body_examples`	No	one example value per body variable, in order — Meta's reviewers read them
`header_example`	No	example value for the header's {{1}}, required when it has one
`call_permission`	No	true asks the customer to allow the business to call them (WhatsApp's call permission request); MARKETING or UTILITY only, and no buttons

Output Schema

TableJSON Schema

Name	Required	Description	Default
`refusal`	No	present only when the call was declined
`template`	No	the submitted template

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 14, 2026

addedInput schema / properties / call_permission

Added value: +{
+  "description": "true asks the customer to allow the business to call them (WhatsApp's call permission request); MARKETING or UTILITY only, and no buttons",
+  "type": "boolean"
+}

addedOutput schema / properties / refusal / properties / account_status

Added value: +{
+  "description": "when the number is not working: its status — starting, not_running, whatsapp_down, suspended, pairing, unlinked or locked",
+  "type": "string"
+}

addedOutput schema / properties / refusal / properties / account_status_reason

Added value: +{
+  "description": "the detail of account_status, e.g. no_egress, stopped, no_plan",
+  "type": "string"
+}

addedOutput schema / properties / refusal / properties / since

Added value: +{
+  "description": "when the number stopped working, RFC3339, when known",
+  "type": "string"
+}

AddedOct 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations declare a non-read-only, non-idempotent write operation. The description goes further by disclosing the review process, approval gating, and Business-number-only constraint, though it omits auth requirements or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose and workflow in a compact paragraph with no filler. Some sentences (categories, variable formatting) duplicate schema details, slightly reducing efficiency.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 11-parameter schema with 100% coverage and an output schema, the description adds essential lifecycle context (review, approval gating, Business-only). It is complete enough for an agent to call correctly without consulting other sources.

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 all 11 parameters. The description repeats variable ordering and example requirements already present in the schema, adding little new semantic detail.

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?

States a specific verb (Submit) and resource (WhatsApp Business message template) and scopes it to Meta's review on Business (Cloud API) numbers. Clearly distinguishable from siblings like wa_delete_template or wa_list_templates.

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?

Explains the approval prerequisite ('only once wa_list_templates shows it APPROVED') and references wa_send_message, giving lifecycle context. It also notes templates apply only to Business numbers, but does not explicitly state when not to use this tool versus an alternative creation path.

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

All whatsmcp tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?