Skip to main content
Glama
wati-io

WhatsApp MCP Server

by wati-io

send_template

Send pre-approved WhatsApp template messages to multiple recipients with custom parameters in a single broadcast.

Instructions

Send template messages to one or more recipients.

Args:
    template_name: Name of the approved template
    broadcast_name: Name for this broadcast batch
    recipients: List of {"phone_number": "...", "custom_params": [{"name": "k", "value": "v"}]}
    channel: Optional channel name or phone (null = default channel)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
template_nameYes
broadcast_nameYes
recipientsYes
channelNo
Behavior2/5

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

No annotations provided. Description does not disclose behavioral traits such as rate limits, whether broadcasts can be overwritten, or if custom_params validation occurs. It implies mutation but lacks detail on side effects or constraints.

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?

Description is brief and to the point, using a docstring-style Args list. Every sentence provides necessary information without redundancy. Suitable for quick parsing.

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

Completeness2/5

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

Missing return value information, which is important for a tool that sends to multiple recipients (success/failure per recipient). Also lacks prerequisites or error conditions. Given no output schema, description should cover more behavioral context.

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 description coverage is 0%, but the description adds meaning: explains each parameter, notably showing recipients structure as a list of objects with phone_number and custom_params. However, it does not clarify additionalProperties or the shape of custom_params fully.

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?

Description clearly states it sends template messages to one or more recipients. This is a specific verb+resource combination that distinguishes it from sibling tools like send_message (plain messages), send_file, and send_interactive.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., template must be approved) or compare with other send tools. The description only lists parameters without contextual usage advice.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/wati-io/wati-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server