Skip to main content
Glama
whatsapp-cloud-mcp

whatsapp-cloud-mcp

Send WhatsApp text message

send_text_message

Send a plain text WhatsApp message to a phone number during the 24-hour customer-service window. Use a template message to begin a new conversation.

Instructions

Send a plain text WhatsApp message to a phone number. Only works inside the 24-hour customer-service window (i.e. the user messaged you in the last 24h). To start a brand-new conversation, use send_template_message instead.

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>",
      "body": "<body>"
    },
    "name": "send_text_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient phone number, ideally E.164 (e.g. +971501234567)
bodyYesMessage text (max 4096 chars)
preview_urlNoRender a link preview for the first URL in the body
reply_to_message_idNoOptional wamid of a message to reply to (shown as a quoted reply)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare openWorldHint and destructiveHint=false; the description adds a substantial behavioral constraint the annotations do not carry — the 24-hour messaging window, which determines whether the call will succeed at all. It stops short of describing failure behavior outside that window (hard error vs. silent drop) or any rate limits, so it is strong but not complete.

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 short sentences, the purpose stated first, the hard constraint second, and the escape hatch last. Every sentence carries a distinct fact and none repeats the schema or annotations.

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?

With no output schema and a simple flat parameter set, the description covers what an agent needs to decide and call: purpose, eligibility condition, and the correct alternative. The remaining gap is what happens when the window is exceeded or the number is invalid, which would help an agent interpret failures.

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 description coverage is 100%, so all four parameters — to, body, preview_url, reply_to_message_id — are already documented with types, length bounds, and examples. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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 opens with a specific verb and resource — 'Send a plain text WhatsApp message to a phone number' — and explicitly distinguishes itself from send_template_message. An agent can tell this apart from send_media_message or send_interactive_buttons based on the 'plain text' qualifier alone.

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?

It states the governing precondition (must be inside the 24-hour customer-service window) and names the exact alternative for the out-of-window case ('use send_template_message instead'). Both the when-to-use and when-not-to-use conditions are explicit rather than inferred.

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