delete_campaign
Delete a campaign and all its steps
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Mailcannon
TDQS
C2.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries full burden. It discloses the cascading deletion of steps, which is a critical behavioral insight. However, it omits other common details like irreversibility, permission requirements, or effect on associated data (e.g., contacts in steps).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness3/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, front-loaded with the action, which is concise. However, it trades off completeness for brevity, lacking details that could be included without significant bloat.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool is destructive and has no annotations or output schema, the description should provide more context about return values, error states, or preconditions. It covers the cascade but not enough for safe invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema has one parameter 'id' with no description and schema coverage is 0%. The description adds no explanation of what 'id' refers to (e.g., campaign ID format, example) leaving the agent to infer meaning from context.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the action ('Delete') and the resource ('a campaign and all its steps'), distinguishing it from siblings like delete_campaign_step which only deletes a single step.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use vs alternatives (e.g., pausing instead of deleting), no prerequisites or consequences mentioned. The description assumes the agent knows when deletion is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
B3.3/5.0
Disambiguation5/5
Each tool targets a distinct action and resource. Campaign lifecycle steps (create, update, delete, schedule, pause, resume) are clearly separate from contact management (add, remove, update tags) and provider/domain operations. No two tools have overlapping purposes.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with underscores (e.g., add_contact, check_domain_deliverability, delete_campaign_step). Mixing of singular/plural nouns (list_campaigns vs list_tags) is intentional and does not break consistency.
Tool Count4/5
34 tools is high but justified for a full-featured email campaign server covering campaigns, contacts, providers, scheduling, deliverability, and task management. A few tools like check_email_spam_score and check_step_spam_score could be merged, but overall the count is reasonable.
Completeness5/5
The tool surface covers the complete CRM lifecycle: campaign CRUD, step management, contact CRUD with tags, provider setup, scheduling, deliverability checks, and spam analysis. Only minor gaps like per-campaign analytics or import/export exist, but core workflows are fully covered.