WhatsMCP: MCP for WhatsApp

List AI Voice-Agent Presets

wa_ai_list_presets

Read-only

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

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON 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.

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"
+]

AddedSep 26, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true), so the bar is lower. The description adds genuinely useful behavioral context: the readiness gate (ready / not_ready_reason) that determines whether a preset is callable, and the expected_variables semantics, going beyond what the annotations declare.

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?

Front-loaded with the purpose, then three tight clauses that each add distinct value (preset composition, call routing via wa_ai_call_start, readiness and variable semantics). No wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description needn't document return fields, and it doesn't waste effort doing so. It supplies everything an agent needs: what a preset is, which sibling consumes it, and the readiness condition gating usage.

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 clarify and the baseline of 4 applies. No parameter-level gaps exist.

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?

States a specific verb (List) and resource (AI voice-agent presets of this workspace), and then defines what a preset actually is. It is clearly distinguishable from siblings like wa_ai_list_calls or wa_list_channels without opening any schema.

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?

Explicitly routes the agent: the preset name is consumed by wa_ai_call_start, and it warns that only ready=true presets can call now, with not_ready_reason as the explanation. It falls just short of a 5 because it doesn't state when to prefer this over the other AI-call-adjacent siblings, but the workflow guidance is clear.

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

All WhatsMCP: MCP for WhatsApp 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?