Skip to main content
Glama
alsaltitop

customer-replies-mcp-server

by alsaltitop

Build WhatsApp Reply Link

replies_whatsapp_link
Read-onlyIdempotent

Build a clickable WhatsApp deep link with a pre-filled message from a template or raw text. The link opens WhatsApp for manual sending, supporting Arabic and English.

Instructions

Compose a reply (from a template + variables, or from raw text) and wrap it in a clickable https://wa.me deep link that opens WhatsApp with the message pre-filled, ready for a human to press send. Arabic and English text both work — the text is URL-encoded as UTF-8.

Args:

  • phone (string): customer's phone number, any formatting accepted (spaces, +, dashes) as long as it includes the country code, e.g. '+966 5x xxx xxxx'. Non-digit characters are stripped automatically.

  • template_id (string, optional): template id from replies_search_templates

  • variables (object, optional): variable name -> value map, used when template_id is given

  • text (string, optional): raw message text, used instead of template_id

Provide either template_id or text (not both, not neither).

Returns: { url, text, missingVariables }. This does NOT send anything — it only builds a link. Opening the link (or the human clicking it) still requires WhatsApp to be installed/logged in on that device; sending is a manual click, nothing is sent automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoRaw message text (alternative to template_id)
phoneYesCustomer phone number with country code, any formatting
variablesNoVariable name -> value map
template_idNoTemplate id to compose from
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds that the tool does not send anything, requires WhatsApp installation, and that non-digit characters in phone are stripped automatically. No contradictions with annotations.

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 well-structured with Args and Returns sections, uses clear language, and no unnecessary words. Every sentence adds value.

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 explicitly lists the return object fields (url, text, missingVariables). It also covers prerequisites (WhatsApp installed) and behavior (manual sending), making it fully self-contained.

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 100% and includes descriptions, but the tool description adds significant value: phone formatting details (non-digit strip), template_id/text exclusivity, and returns structure. This goes beyond mere repetition.

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 composes a reply and wraps it in a clickable wa.me deep link. It explicitly says 'This does NOT send anything — it only builds a link,' distinguishing it clearly from sending tools like replies_compose_reply.

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

Usage Guidelines5/5

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

The description provides explicit guidance: when to use (build a link), when not (it does not send), and constraints between template_id and text. It also clarifies that WhatsApp must be installed and sending is manual.

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/alsaltitop/customer-replies-mcp-server'

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