Skip to main content
Glama

WhaTools — WhatsApp tools

generate_bulk_whatsapp_links

Generate personalized WhatsApp click-to-chat (wa.me) links for a list of contacts from one message template. Everything uses a single {{…}} syntax: {{field}} placeholders are replaced per contact; {{field|fallback}} supplies a default for empty/missing fields; {{FirstName}} is derived from a name field; and {{option a|option b}} spintax (a group whose first option is not a field) picks one variation per contact (stable per number) so messages are not identical. Returns a JSON array of {phone, message, link}. Runs locally; no message is sent: each link opens WhatsApp with the text pre-filled and a human taps send.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contactsYesUp to 500 contacts. Each needs a "phone" (international format, digits only) plus any placeholder fields as string properties.
templateYesMessage template with {{field}} placeholders, e.g. 'Hello {{name}}, see you at {{time}}'. Supports {{field|fallback}} defaults, {{FirstName}} derived from a name field, and {{a|b|c}} spintax variation (a {{…}} group whose first option isn't a field). Placeholder matching is case-insensitive; WhatsApp formatting (*bold*, _italic_) is kept.

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?

It explicitly discloses that no message is sent, the operation runs locally, and each link opens WhatsApp with pre-filled text requiring human action to send. This fully covers side effects.

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 thorough but each sentence adds necessary detail about the single-template constraint, placeholder syntax, output format, and safety guarantee. No redundant content.

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 complexity of the template syntax and bulk operation, the description fully covers what the tool does, its return format, and its non-sending behavior, leaving no critical 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?

The schema already covers the parameters and placeholder syntax. The description adds useful detail on case-insensitivity and preserving WhatsApp formatting, going modestly beyond the schema.

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 clearly states the tool generates personalized WhatsApp click-to-chat links for a list of contacts from a single template, which distinguishes it from sibling tools like generate_whatsapp_link that handle individual links.

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?

The description implies the use case (bulk generation for many contacts) but does not explicitly mention alternatives such as 'use this instead of the single-link tool when you have multiple contacts.'

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.