Skip to main content
Glama

Send WhatsApp template

whatsapp_send_template
Destructive

Sends an approved WhatsApp template message to one recipient; templates can be sent outside the 24-hour session window. Variables map placeholder numbers to values, e.g. {"1":"Rahul","2":"15 Jul"}. With dryRun: true it returns the message that would be sent, without 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>",
      "templateName": "<templateName>"
    },
    "name": "whatsapp_send_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient in international format, e.g. +919876543210
dryRunNo
languageNoTemplate language code, default en
variablesNoBody variables keyed by placeholder number, e.g. {"1":"Rahul"}
templateNameYesApproved template name

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 declare destructiveHint=true and idempotentHint=false, but the description adds real behavioral context: the 24-hour session rule and a dryRun mode that returns the would-be payload without sending. What is missing is the risk side of destructiveHint — no mention of billing/cost, rate limits, or what happens on invalid template or recipient failure.

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?

Three compact clauses: what it does and its session-window advantage, how variables map, then the dryRun escape hatch. Purpose is front-loaded and every sentence carries distinct information with no filler.

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 5-parameter send tool with a nested variables object and no output schema, the description covers the key unknowns: the session-window rule, variable keying, and the dryRun return behavior. It does not say what a successful send returns (message id/status) or how errors surface, which is a modest remaining gap.

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

Parameters4/5

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

Schema coverage is 80%, so the baseline is 3; the description earns an extra point by giving dryRun semantic meaning (returns the message without sending) that the bare boolean in the schema lacks. The variables example is useful though it largely duplicates the schema's own example.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Sends an approved WhatsApp template message to one recipient') and scopes it to template messages, which implicitly separates it from the freeform whatsapp_send_text sibling. It does not explicitly name or route against any sibling, so it stops short of a 5.

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?

Gives a concrete selection signal by noting templates can be sent outside the 24-hour session window, which is exactly the condition under which an agent picks this over a plain text send. It also documents the dryRun preview path. No explicit exclusions or named alternatives, so not a 5.

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.