Skip to main content
Glama

Delete a campaign

delete_campaign
DestructiveIdempotent

Use this when the user wants a campaign deleted for good. Nothing more is sent from it; its people and lists are kept. It cannot be restored. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "campaignId": "<campaignId>"
    },
    "name": "delete_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYesThe campaign's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's real contribution is the blast radius: what is removed (the campaign), what survives (people and lists), and that the action is irreversible. It adds no info on permissions, behavior for an actively running campaign, or whether a confirmation step is expected; the trailing "Free." is ambiguous.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four short clauses, front-loaded with the use case and followed immediately by the consequences. The only weak element is the closing fragment "Free.", which is too terse to convey its meaning unambiguously.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter destructive tool with rich annotations and no output schema, the description covers the essential behavioral facts: permanence and the preserved entities. Only authorization requirements and preconditions for deleting a live campaign are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with a single required campaignId fully documented including pattern and length constraints. The description adds no meaning beyond the schema for this parameter, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"a campaign deleted for good" gives a specific verb and resource, and "its people and lists are kept" scopes what is and isn't removed, which separates it from delete_campaign_step or delete_list in the sibling set. It stops short of naming a sibling explicitly, so it lands just under a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Use this when the user wants a campaign deleted for good" states the triggering condition clearly, and "It cannot be restored" implicitly steers the agent away from using it for reversible operations. No alternative (e.g. pausing or stopping a campaign) is named as a fallback, so guidance is clear but not exhaustive.

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.

Resources