delete_campaign
Permanently delete a campaign.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| bot_id | Yes | ||
| campaign_id | Yes |
Permanently delete a campaign.
| Name | Required | Description | Default |
|---|---|---|---|
| bot_id | Yes | ||
| campaign_id | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral burden. It usefully discloses that deletion is permanent, signaling an irreversible destructive action, but it omits permissions required, side effects such as whether associated campaign data is also removed, and whether any confirmation is needed.
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 wasted words. The destructive qualifier 'Permanently' appears before the resource, which is the most important information for an agent.
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?
This is a destructive mutation tool with no annotations, no output schema, and zero parameter description coverage. One short sentence conveys permanence but leaves out prerequisite context, side effects, and parameter semantics needed for confident invocation.
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%, and two parameters are required. The description mentions 'campaign' but does not explain the meaning, format, or relationship of bot_id and campaign_id, so it does not 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?
The description states a specific verb and resource: 'delete' plus 'campaign', with the important qualifier 'Permanently'. This distinguishes it from create_campaign, update_campaign, and list_campaigns by operation, though it does not explicitly name alternatives or clarify the bot/campaign relationship.
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?
There is no guidance on when to use this tool versus alternatives such as update_campaign, nor any prerequisites or confirmation steps. The word 'Permanently' implies caution, but no explicit when/when-not conditions are given.
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.