sendpulse_list_flowsList all automation flows configured for a specific SendPulse WhatsApp bot to inspect its automated responses and sequences.
List all automation flows configured for a bot.
| Name | Required | Description | Default |
|---|---|---|---|
| bot_id | Yes | Bot ID (from sendpulse_list_bots) | |
| account | No | Account name (only one configured: brand_a) | brand_a |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered. The description only adds the scoping fact that results are per-bot; it says nothing about ordering, result size, or what happens if the bot has no flows.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler. Nothing is wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only list tool with full schema coverage and complete safety annotations, this is nearly sufficient. Only pagination/return-shape detail is missing, and no output schema exists to cover it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the bot_id description even cross-references sendpulse_list_bots, so the schema carries the parameter burden. The description adds no syntax or format detail beyond that baseline.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (List) and resource (automation flows) with scope limited to a bot. It does not explicitly differentiate itself from siblings like sendpulse_run_flow or sendpulse_list_triggers, but the purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this versus alternatives such as sendpulse_run_flow or sendpulse_list_triggers, and no preconditions beyond the implicit need for a bot_id. Usage is only inferable from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.