Skip to main content
Glama

DripRaven WhatsApp campaigns

create_template

Create a new WhatsApp message template on the connected WhatsApp Business Account. Placeholders in body/header/URL use positional {{1}}, {{2}} … syntax. IMPORTANT — personalisation: for EVERY body placeholder you MUST set variable_mapping so it fills with each contact's real data at send time. Map {{1}} to a contact field: { "1": "name" } fills {{1}} with the contact's name; { "1": "name", "2": "fields.plan_tier" } maps a custom field. Without a mapping the placeholder sends as a blank space to everyone — NOT the sample value. body_examples is a SEPARATE thing: one sample value per placeholder (e.g. a name like Alex) used ONLY to satisfy Meta's approval review; it is never sent to a contact. Meta REQUIRES body_examples when the body has placeholders, so supply BOTH body_examples (for approval) and variable_mapping (for real personalisation). name must be lowercase letters, numbers and underscores. category is MARKETING, UTILITY, or AUTHENTICATION. New templates start PENDING Meta review — only APPROVED templates can be broadcast (poll with sync_templates / list_templates). VIDEO HEADER: pass header_video_url with a public link to an .mp4 to attach/embed a video at the top of the message; it is uploaded to WhatsApp for approval and re-sent with every broadcast. A template has ONE header, so set header_text OR header_video_url, not both. Returns the stored template row (or { id, status }).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesBody text; use {{1}}, {{2}} … for variables
nameYesLowercase a-z, 0-9 and underscores, e.g. order_update
buttonsNo
categoryYes
languageNoLanguage code, default "en_US"
footer_textNoOptional footer text
header_textNoOptional text header (max 1 placeholder). Mutually exclusive with header_video_url
body_examplesNoMeta approval sample for each body placeholder, in order ({{1}}, {{2}}, …). For Meta review only — NEVER sent to a contact. Use variable_mapping for real personalisation.
header_video_urlNoPublic URL of an .mp4 to attach/embed as a video header. Mutually exclusive with header_text. WhatsApp reviews the video before the template can send.
variable_mappingNoMaps each placeholder number to the contact field that fills it at send time, e.g. { "1": "name", "2": "fields.plan_tier" }. Set one entry per body placeholder or it sends blank. Values: a top-level field (name) or fields.<key> for a custom field.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes far beyond the annotations by disclosing crucial behavioral pitfalls: unset variable_mapping sends blank placeholders, body_examples are only for Meta review and never sent, video headers are uploaded and re-sent with every broadcast, and header_text/header_video_url are mutually exclusive. This is exactly the kind of non-obvious behavior an agent needs.

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?

Long but justifiably so given 10 parameters and Meta-specific approval rules. The most critical warning about variable_mapping is front-loaded, and the video header section is separated. Slight redundancy around body_examples and variable_mapping keeps it from a perfect score.

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?

Despite lacking an output schema, the description states what is returned. It also covers the full lifecycle context, approval flow, parameter constraints, and the key distinction between placeholders and examples. An agent has everything needed to call this tool correctly and avoid common failures.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already high, but the description adds substantial meaning beyond it: concrete variable_mapping syntax including custom fields like fields.plan_tier, the critical distinction between body_examples and variable_mapping, and the failure mode when mappings are omitted. This materially improves correct invocation.

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 action and resource: 'Create a new WhatsApp message template on the connected WhatsApp Business Account.' It clearly distinguishes from siblings like update_template, delete_template, and list_templates by focusing on creation and the template lifecycle.

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?

Provides strong contextual guidance: new templates start PENDING review, only APPROVED templates can be broadcast, and users should poll sync_templates/list_templates. It does not explicitly name an alternative tool for modifying existing templates, but the context makes the intended use unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources