Remove an audience list while retaining all contacts. Only the list and its memberships are deleted.
Delete an audience (list). Contacts are not deleted — only the list and its memberships are removed.
| Name | Required | Description | Default |
|---|---|---|---|
| apiKey | No | Send16 API key (overrides SEND16_API_KEY env var) | |
| audienceId | Yes | Audience ID |
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 carries full burden. It discloses that only the list and memberships are removed, not the contacts themselves. However, it does not cover potential side effects, authorization requirements, or rate limits, leaving some gaps for a deletion tool.
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?
Two sentences with no fluff. Front-loads the action and essential caveat. Every sentence is necessary and well-structured.
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 the lack of output schema and only two simple parameters, the description is fairly complete. It explains the core operation and clarifies the effect on contacts. Missing return value info is acceptable for a simple delete operation.
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% with descriptions for both parameters (apiKey, audienceId). The description offers no additional meaning beyond what the schema provides, placing it at baseline 3.
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 'Delete an audience (list)' using a specific verb and resource. It further clarifies that contacts are not deleted, distinguishing this tool from similar operations like removing contacts from 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 explicit guidance is given on when to use this tool versus alternatives such as remove_contact_from_audience or add_contacts_to_audience. The description implies usage by stating what happens, but lacks when-not-to-use or workflow context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.