Skip to main content
Glama
Sign In

WhatsApp Business API by Wassenger

by com.wassenger
OverviewDiscussionsAdmin

list_whatsapp_flow_responses

Read-only

List what customers answered in a WhatsApp Form (Meta WhatsApp Flow), newest first: who answered, each question's label and value, and when. Takes the form's id from list_whatsapp_flows (not its flowId). Only keys of the account owner or an admin can read answers.

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": {
      "form_id": "<form_id>"
    },
    "name": "list_whatsapp_flow_responses"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD (UTC)
fromNoFirst day, YYYY-MM-DD (UTC)
pageNoPage, from 0
sizeNoAnswers per page (default 25, max 100)
deviceNoOnly answers received on this number
form_idYesThe form id ("id" from list_whatsapp_flows, 24 hex characters)
campaignNoOnly answers to this campaign

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful behavior: results are newest first, include who answered, question labels/values, and timestamps, and require owner/admin credentials. It does not discuss rate limits or error behavior, but adds meaningful 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?

The description is two tight sentences with no wasted language. Purpose and return shape are front-loaded, followed by the key id-source warning and permission caveat.

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, the description does a good job listing the returned content and ordering, while the schema covers filters and pagination inputs. A minor gap remains around the full response envelope and pagination metadata, but the definition is otherwise complete for this read-only list tool.

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 description coverage is 100%, so the baseline is 3. The description adds a useful disambiguation for the required form_id parameter: it comes from list_whatsapp_flows and not the flowId. It does not add meaning for the other six parameters beyond the schema, so it is above baseline but not exhaustive.

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 states a specific verb and resource: list what customers answered in a WhatsApp Form. It also distinguishes the form id from the flowId, which prevents confusion with list_whatsapp_flows. The return fields and newest-first ordering make the tool's purpose immediately clear.

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

Usage Guidelines4/5

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

It explicitly says to take the form id from list_whatsapp_flows rather than its flowId, which is a concrete prerequisite and alternative reference. It also states the owner/admin key restriction. It does not explicitly frame when to choose this over other WhatsApp tools beyond that prerequisite, so it is strong but not complete.

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

All WhatsApp Business API by Wassenger toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources