reddit_ads_delete_custom_audiencePermanently delete a Reddit Ads custom audience by supplying its audience ID, removing the segment from active campaign use.
Permanently delete a custom audience.
| Name | Required | Description | Default |
|---|---|---|---|
| audience_id | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so safety is covered. The description adds only the word 'Permanently', which usefully signals non-reversibility, but it omits cascading effects, whether deletion is synchronous, or required permissions.
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 zero waste and the destructive nature signalled first. Brevity here edges toward under-specification rather than poor structure.
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 an irreversible delete with no output schema and an undocumented parameter, the description should cover recoverability, prerequisites, and side effects on dependent entities. None of that is present, so an agent lacks enough to invoke it safely.
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 0% for the single required parameter audience_id, and the description never mentions it. An agent gets no help on where to obtain the ID or its expected format, so the description fails to compensate for the schema gap.
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 (delete) and resource (custom audience) with the permanence qualifier. It does not differentiate from siblings such as reddit_ads_delete_catalog or reddit_ads_update_custom_audience_users, but the core action 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 updating or listing audiences, no prerequisites (e.g., audience must exist), and no note about the effect on campaigns or ad groups currently targeting the audience. 'Permanently' hints at irreversibility but stops short of actionable context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.