Skip to main content
Glama
rukman7

whatsapp-mcp-server

by rukman7

Send Interactive List

whatsapp_send_list

Send a WhatsApp message containing an interactive menu list with options grouped in sections, letting recipients choose from customizable rows.

Instructions

Send a message with a menu list of options.

Args:

  • to (string): Recipient phone number

  • body_text (string): Main message body

  • button_text (string): Text on the list menu button

  • sections (string): JSON array of sections with rows

  • header_text (string, optional): Header text

  • footer_text (string, optional): Footer text

Returns: Message ID and delivery status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesRecipient phone number in international format (e.g. '353851234567' or '+353851234567')
sectionsYesJSON string of sections array. Example: '[{"title":"Section 1","rows":[{"id":"row1","title":"Option 1","description":"Desc"}]}]'
body_textYesMain body text of the message
button_textYesText for the list menu button
footer_textNoOptional footer text
header_textNoOptional header text
response_formatNoOutput format: 'markdown' for human-readable or 'json' for structured datamarkdown
Behavior4/5

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

Annotations already indicate this is a write operation (readOnlyHint=false), and the description adds that it returns 'Message ID and delivery status,' which gives the agent a clearer expectation of the tool's outcome. It does not explicitly mention external side effects beyond sending, but the annotations (openWorldHint=true) cover the external interaction. The description provides modest additional behavioral 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured: a clear first sentence followed by an Args list and Returns line. It is relatively concise, though the Args list duplicates information already present in the schema. The structure makes it easy to scan, but the duplication could be trimmed.

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?

Given the rich schema with full parameter descriptions and the presence of annotations (openWorldHint, readOnlyHint), the description covers the essential operational aspects: what the tool does, key parameters, and return value. It does not include usage timing or edge cases, but these are not critical for a straightforward send tool. The description is sufficiently complete for the agent to invoke the tool correctly.

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?

Input schema covers 100% of parameters with detailed descriptions, including examples for 'sections' and format details for 'response_format.' The description's Args list only restates parameter names and short descriptions, adding no new meaning beyond what the schema already provides. Therefore, the baseline of 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 'Send a message with a menu list of options,' which clearly identifies the tool's verb (send), resource (message with menu list), and distinguishes it from sibling WhatsApp send tools (text, image, buttons, etc.). The title 'Send Interactive List' reinforces this specific function.

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 description does not explicitly state when to use this tool versus alternatives like whatsapp_send_buttons or whatsapp_send_text. The use case is implied by the phrase 'menu list of options,' but there is no direct comparison or exclusion of other message types. This makes the guidance implicit rather than explicit.

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/rukman7/whatsapp-mcp-server'

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