Find and manage email campaigns by filtering by status and using pagination.
List email campaigns with optional status filtering and pagination.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number | |
| apiKey | No | Send16 API key (overrides SEND16_API_KEY env var) | |
| status | No | Filter campaigns by status | |
| pageSize | No | Results per page (max 100) |
Changes observed during successful MCP inspections.
v0.5.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavior. It states listing with filtering and pagination, which is clear but lacks details on authentication, rate limits, or result shape. It is adequate but not thorough.
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?
The description is a single, front-loaded sentence with no extraneous information. Every word contributes value.
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 tool with 4 optional parameters and no output schema, the description is minimal. It does not explain return format, error handling, or pagination behavior beyond what the schema provides. Adequate but not complete.
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%, so each parameter is already documented. The description reinforces the purpose of status and pagination but adds no new meaning beyond the schema.
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 'List email campaigns with optional status filtering and pagination' uses a specific verb-resource pair, clearly distinguishing it from sibling tools like list_actions or list_audiences.
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 is provided on when to use this tool versus alternatives such as list_campaign_stats or get_campaign_stats. The description does not mention exclusions or context for usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.