Skip to main content
Glama

Delete a campaign template

delete_campaign_template
DestructiveIdempotent

Use this when the user wants a campaign template removed. Campaigns already made from it keep their steps. 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": {
      "templateId": "<templateId>"
    },
    "name": "delete_campaign_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateIdYesThe template's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety bar is lower; the description still adds genuinely non-redundant behavior: campaigns derived from the template keep their steps, and the deletion is irreversible. The trailing 'Free' adds a cost note, though its meaning is somewhat cryptic.

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 sentences, front-loaded with the trigger, followed immediately by the two consequences that matter most for a delete. No padding, though the standalone 'Free' fragment is too terse to be self-explanatory.

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 delete with no output schema and strong annotation coverage, the description supplies exactly the missing pieces: irreversibility and the effect on derived campaigns. Only a pointer on where to find a valid templateId is absent.

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?

With one parameter at 100% schema description coverage, the schema already documents templateId and its 24-character hex constraint. The description adds no format, lookup, or source guidance for obtaining the id, so the baseline 3 holds.

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?

The description states a specific verb and resource: 'a campaign template removed,' which pairs the operation with the exact object, distinguishing it from delete_campaign or delete_campaign_step. It never names an alternative sibling, so the differentiation is inferred from the resource noun rather than made explicit.

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

Usage Guidelines3/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 template removed' gives a clear triggering condition but no exclusions, prerequisites, or named alternatives such as list_campaign_templates or delete_campaign. Usage is implied by the trigger phrase only.

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