list_dealsList CRM deals (sales pipeline opportunities). Returns deal IDs, titles, values, stages, and owners with meta.total.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 20, max 100). | |
| _apiKey | Yes | ActiveCampaign API key (UI: Settings → Developer). | |
| account | Yes | Your ActiveCampaign account URL or subdomain, e.g. "https://youraccount.api-us1.com" or just "youraccount". |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "_apiKey": "your-activecampaign-api-key",
+ "account": "myaccount",
+ "limit": 25
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations (readOnlyHint, idempotentHint, etc.) already indicate safe read operations. The description adds value by detailing the response structure (deal IDs, titles, values, stages, owners, meta.total), which goes beyond annotations.
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?
Single sentence front-loading the action and resource, followed by concise details on return fields. No extraneous words.
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?
No output schema is provided, but the description compensates by listing returned fields. It covers the essential information for a list tool, though additional details on pagination or sorting are absent.
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 coverage is 100%, so each parameter already has a description. The tool description does not add parameter-level meaning beyond the schema, meeting baseline expectations.
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?
The description clearly states the tool lists CRM deals (sales pipeline opportunities) and specifies the returned fields (deal IDs, titles, values, stages, owners, meta.total). It is distinct from sibling list tools like list_contacts or list_campaigns.
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 explicit guidance on when to use this tool versus sibling list tools. The description is functional but lacks context about preferred scenarios or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.