Skip to main content
Glama
whatsapp-cloud-mcp

whatsapp-cloud-mcp

Send WhatsApp reply buttons

send_interactive_buttons

Sends WhatsApp messages with up to three quick-reply buttons; taps return button id and title to your webhook, enabling guided user responses within an open 24-hour service window.

Instructions

Send up to 3 quick-reply buttons with a message. The user's tap is delivered to your webhook as a button reply (id + title). Requires an open 24-hour customer-service window.

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>",
      "buttons": "<buttons>"
    },
    "name": "send_interactive_buttons"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient phone number, ideally E.164 (e.g. +971501234567)
bodyYesMain message text
footerNoOptional footer text
headerNoOptional text header
buttonsYes1–3 quick-reply buttons
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

A3.8/5.0
Behavior4/5

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

Annotations already mark this as non-destructive and open-world, and the description adds meaningful behavior: taps are delivered to the webhook as id+title button replies and an open 24-hour window is required. It does not cover rate limits or response behavior more fully, but it adds useful context beyond the 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?

Three concise sentences front-load purpose, then delivery behavior, then the key prerequisite. No filler; every sentence contributes.

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 send tool with fully documented schema parameters and no output schema, the description supplies the essential operational context: button limit, webhook delivery, and the 24-hour window. It could mention sibling alternatives more explicitly, but the core invocation context is complete.

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 six parameters—including recipient, body, header/footer, buttons, and reply_to_message_id—are documented in the schema. The description only restates the 3-button limit and the id/title payload; it adds no significant meaning beyond the schema.

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?

The description states a specific action—sending up to three quick-reply buttons with a message—so the verb and resource are clear. It does not explicitly contrast with sibling tools such as send_interactive_list or send_text_message, so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

The implied use case is quick replies, but the description does not explicitly say when to choose buttons over lists, templates, or plain text. The 24-hour customer-service window is a prerequisite rather than an alternative-selection rule.

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