Skip to main content
Glama
whatsapp-cloud-mcp

whatsapp-cloud-mcp

Send WhatsApp list message

send_interactive_list

Send a tappable WhatsApp list menu (up to 10 rows across sections) and deliver the user's selection to your webhook as an id+title list reply; needs an open 24-hour service window.

Instructions

Send a tappable list menu (up to 10 rows total across sections). The user's selection is delivered to your webhook as a list 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>",
      "button_text": "<button_text>",
      "sections": "<sections>"
    },
    "name": "send_interactive_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesRecipient phone number, ideally E.164 (e.g. +971501234567)
bodyYes
footerNo
headerNo
sectionsYes
button_textYesLabel of the button that opens the list

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?

The description adds behavior beyond the annotations: it explains that the user's selection returns asynchronously as a webhook list reply containing id and title, and that an open 24-hour window is required. These are the two facts an agent most needs for a WhatsApp send, though nothing is said about failure behavior when the window is closed or about rate limits.

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 with no filler: capability first, delivery mechanism second, prerequisite last. Every clause carries information an agent would otherwise have to guess.

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?

There is no output schema, and the description compensates by describing the webhook reply payload, which is effectively the return path. Combined with the row cap and window prerequisite, this is close to sufficient for a 6-parameter send tool; only failure modes and the unelaborated formatting parameters remain thin.

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?

At 33% schema coverage the description has to carry weight, and it partially does by explaining that rows are capped at 10 across sections and that row id/title come back in the reply. The remaining parameters (to, body, header, footer, button_text) get no elaboration, so half the surface is still undocumented.

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?

"Send a tappable list menu" gives a specific verb plus resource, and the parenthetical "up to 10 rows total across sections" pins down the shape of the payload, which separates it from the sibling send_interactive_buttons. It never names a sibling explicitly, so the differentiation is inferred rather than stated.

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 24-hour customer-service window is a real prerequisite that tells the agent when the call will succeed, which is useful context. However, there is no guidance on when to choose a list menu over buttons or a plain text message, so the choice among siblings is left to inference.

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