Retrieve active and historical enrollments for a specific automation by automation ID, with optional filtering by state and pagination.
List active and historical enrollments for an automation.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| state | No | ||
| apiKey | No | Send16 API key (overrides SEND16_API_KEY env var) | |
| cursor | No | ||
| automationId | Yes | Automation ID |
Changes observed during successful MCP inspections.
v0.5.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, and description lacks behavioral details such as pagination (cursor parameter not explained), authentication (apiKey only hinted), rate limits, or whether it returns full enrollment objects. Insufficient disclosure for a list endpoint.
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-loaded with key information, no unnecessary words. Highly concise.
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?
Given 5 parameters and no output schema or annotations, description is incomplete. Missing explanation of pagination, filter options, return format, and required state parameter behavior. Not sufficient for an agent to use correctly without additional hints.
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?
With only 40% schema description coverage, description does not compensate. Does not explain state enum values, cursor usage, or limit meaning beyond what schema provides. The mention of 'active and historical' only vaguely hints at the state filter.
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?
Description uses specific verb 'List' and resource 'enrollments for an automation', clarifying scope with 'active and historical'. Clearly distinguishes from siblings like 'enroll_in_automation' and 'list_automations'.
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 tool versus alternatives like 'list_automations' or 'get_automation_stats'. No prerequisites or exclusions mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.