whatsmcp

List AI Voice-Agent Presets

wa_ai_list_presets

Read-only

[Not usable in this workspace: it acts on every number, and not every number's plan includes it — calling it returns a plan_required refusal; wa_get_plan lists each number's plan.] List the AI voice-agent presets of this workspace. A preset pairs a voice agent with one of your WhatsApp numbers (the line it calls from) and default variables. Use a preset's name with wa_ai_call_start; only presets with ready=true can call now (not_ready_reason says why otherwise). expected_variables are the variables the agent's prompt uses — pass them to wa_ai_call_start.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`presets`	Yes	your presets; call wa_ai_call_start with a preset whose ready is true
`refusal`	No	present only when the request was declined

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

changedOutput schema / properties / refusal / properties / account_status / description

Previous value: -"when the number is not working: its status — starting, not_running, whatsapp_down, suspended, pairing, unlinked or locked"New value: +"when the number is not working: its status — starting, not_running, whatsapp_down (telegram_down for a Telegram account), suspended, pairing, unlinked or locked"

Changed1 schema field changedOct 26, 2026

addedOutput schema / properties / refusal / properties / candidates

Added value: +{
+  "description": "on an account_ambiguous refusal: the accounts to choose from — retry with one of these as account_id",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "account_id": {
+        "description": "the id to retry with as account_id",
+        "type": "string"
+      },
+      "name": {
+        "description": "the account's WhatsApp display name",
+        "type": "string"
+      },
+      "phone": {
+        "description": "the account's phone number, E.164",
+        "type": "string"
+      },
+      "status": {
+        "description": "whether the number works right now — live, connecting, or why not, as wa_list_accounts reports it",
+        "type": "string"
+      }
+    },
+    "required": [
+      "account_id"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

Changed3 schema fields changedOct 14, 2026

addedOutput schema / properties / refusal / properties / account_status

Added value: +{
+  "description": "when the number is not working: its status — starting, not_running, whatsapp_down, suspended, pairing, unlinked or locked",
+  "type": "string"
+}

addedOutput schema / properties / refusal / properties / account_status_reason

Added value: +{
+  "description": "the detail of account_status, e.g. no_egress, stopped, no_plan",
+  "type": "string"
+}

addedOutput schema / properties / refusal / properties / since

Added value: +{
+  "description": "when the number stopped working, RFC3339, when known",
+  "type": "string"
+}

Changed3 schema fields changedSep 28, 2026

addedOutput schema / properties / presets / items / properties / ring_delay_secs
```
Added value: +{
+  "type": "integer"
+}
```
addedOutput schema / properties / presets / items / properties / start_delay_secs
```
Added value: +{
+  "type": "integer"
+}
```

changedOutput schema / properties / presets / items / required

Previous value: -[
-  "id",
-  "name",
-  "description",
-  "provider",
-  "agent_id",
-  "agent_name",
-  "account_id",
-  "line",
-  "default_variables",
-  "expected_variables",
-  "enabled",
-  "answers_inbound",
-  "ready"
-]New value: +[
+  "id",
+  "name",
+  "description",
+  "provider",
+  "agent_id",
+  "agent_name",
+  "account_id",
+  "line",
+  "default_variables",
+  "expected_variables",
+  "enabled",
+  "answers_inbound",
+  "ring_delay_secs",
+  "start_delay_secs",
+  "ready"
+]

Changed2 schema fields changedSep 28, 2026

addedOutput schema / properties / presets / items / properties / answers_inbound
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / properties / presets / items / required

Previous value: -[
-  "id",
-  "name",
-  "description",
-  "provider",
-  "agent_id",
-  "agent_name",
-  "account_id",
-  "line",
-  "default_variables",
-  "expected_variables",
-  "enabled",
-  "ready"
-]New value: +[
+  "id",
+  "name",
+  "description",
+  "provider",
+  "agent_id",
+  "agent_name",
+  "account_id",
+  "line",
+  "default_variables",
+  "expected_variables",
+  "enabled",
+  "answers_inbound",
+  "ready"
+]

First observedSep 27, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the read-only profile, and the description adds real behavioral context the annotations cannot: calling it returns a plan_required refusal in this workspace, readiness is exposed via ready/not_ready_reason, and presets carry expected_variables. The opening caveat and the subsequent description of normal listing behavior pull in opposite directions, which costs a point on coherence even though the disclosure itself is valuable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The core definition and the wa_ai_call_start routing are front-loaded and efficient, but the bracketed preamble is dense and delivers a mixed message before the reader knows what the tool is. Three of the four sentences earn their place; the caveat could be a single clear clause.

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?

An output schema exists, so return values need not be spelled out, yet the description still explains ready/not_ready_reason and expected_variables enough to act on. The only completeness gap is that it never resolves the tension between 'not usable in this workspace' and the normal listing instructions.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description's discussion of ready and expected_variables refers to returned fields rather than inputs, so it neither helps nor hurts here.

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 core sentence is a specific verb+resource ('List the AI voice-agent presets') and it goes further by defining what a preset is (voice agent + WhatsApp line + default variables), which distinguishes it from wa_ai_list_calls. The bracketed preamble saying it is 'Not usable in this workspace' muddies the stated purpose and makes the agent wonder whether the tool is callable at all.

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 routes clearly downstream: use the preset's name with wa_ai_call_start, pass expected_variables there too, and only presets with ready=true can call now. It also points to wa_get_plan for per-number plan information. What it lacks is an explicit statement of when to consult presets versus the sibling wa_ai_list_calls/wa_ai_call_get tools.

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

All whatsmcp tools Inspect

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

Need Help?