WhatsMCP: MCP for WhatsApp

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

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

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.

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / refusal / properties / candidates

Added value: +{
+  "description": "on an account_ambiguous refusal: the accounts to choose from — retry with one of these as account_id",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "account_id": {
+        "description": "the id to retry with as account_id",
+        "type": "string"
+      },
+      "name": {
+        "description": "the account's WhatsApp display name",
+        "type": "string"
+      },
+      "phone": {
+        "description": "the account's phone number, E.164",
+        "type": "string"
+      },
+      "status": {
+        "description": "whether the number works right now — live, connecting, or why not, as wa_list_accounts reports it",
+        "type": "string"
+      }
+    },
+    "required": [
+      "account_id"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

Changed4 schema fields changedOct 11, 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 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond annotations, the description discloses the asynchronous Meta review process, typical review duration, and the APPROVED-gating requirement before the template can be used. It also clarifies that body variables must be numbered in order with one example per variable, which is important behavioral context for submission.

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 front-loaded with the core action and review workflow, then adds only high-value constraints about categories, variables, examples, and Business-only applicability. Every sentence carries useful information without unnecessary repetition.

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, full schema coverage, annotations, and an output schema, the description provides the necessary workflow context: review, approval gating, Business-number restriction, category constraints, and variable/example expectations. An agent has enough information to invoke the tool correctly without needing return-value details in the description.

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 schema already documents all 11 parameters in detail. The description reinforces category, body-variable ordering, and body_examples alignment, but most parameter semantics are carried by the schema rather than the description, making 3 the appropriate baseline.

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 states a specific verb and resource: submit a new WhatsApp Business message template for Meta review on a Business (Cloud API) number. It also distinguishes the creation action from downstream use by naming wa_list_templates for approval status and wa_send_message for sending an approved template.

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?

Usage context is clear: this creates a template for Meta review, templates only apply to Business numbers, categories must be MARKETING or UTILITY, and sending is only possible after wa_list_templates shows APPROVED. It does not explicitly contrast with sibling operations like wa_delete_template, but the create-specific purpose is unambiguous.

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

All WhatsMCP: MCP for WhatsApp 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?