Skip to main content
Glama

whatsapp_templates_write

Destructive

Create, edit or delete WhatsApp message templates. New and edited templates go to Meta for review before they can be used. Placeholders are {{1}}, {{2}}… in order. Actions: create — submit a new template; give bodyText or components Needs: name, category, language. | update — replace the components (and optionally category) of an existing template Needs: templateId, components. | delete — delete a template by name (all languages unless templateId is given) Needs: name.

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": {
      "action": "<action>",
      "agentId": "<agentId>",
      "phoneId": "<phoneId>"
    },
    "name": "whatsapp_templates_write"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNocompact (default) = light mode: long text is cut and bulky blobs are replaced by a size marker. full = complete API response.
nameNoFor create: lowercase letters, digits and underscores. For delete: the template name.
actionYes
agentIdYes
phoneIdYesMeta WhatsApp phone number ID (from get_agent_channels), not the phone number.
bodyTextNoFor create: body text of a simple text-only template.
categoryNo
languageNoFor create: language code, e.g. "en_US", "ar".
componentsNoMeta template components (HEADER / BODY / FOOTER / BUTTONS) for create or update, when more than a plain body is needed.
templateIdNoFor update (required) and delete (optional).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already disclose destructiveHint=true and readOnlyHint=false, and the description adds non-obvious behavior that the annotations cannot: templates enter Meta review before use, placeholder numbering convention, and that delete removes all language variants unless templateId is supplied. It does not mention whether deleted templates can be recovered.

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-loaded purpose sentence, then a compact action list with per-action requirements — no filler. The piped action block is dense but scannable and strictly on-topic.

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 10-param, multi-action mutation tool with no output schema, the description covers the review lifecycle, placeholders, and per-action parameter requirements. Minor gaps remain around the undocumented agentId and what a successful response or review rejection looks like.

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 70%, so the schema already documents most fields. The description does add useful conditional mapping (which params belong to which action, and that templateId makes delete language-specific), but leaves agentId unexplained and does not clarify the interaction between bodyText and components or the compact/full mode.

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 set plus resource (create/edit/delete WhatsApp message templates) and enumerates the three supported actions with their individual semantics. An agent can distinguish this from the read-only sibling whatsapp_templates_read without opening either schema.

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?

Each action carries an explicit 'Needs:' prerequisite list (create → name/category/language and bodyText or components; update → templateId/components; delete → name with optional templateId), which is real when-to-use guidance. It stops short of naming the read sibling as the alternative for listing or inspecting templates.

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