Skip to main content
Glama
Sign In

Mailercloud

by io.github.mailercloud-com
OverviewDiscussionsAdmin

Delete Campaign (preview, then confirm)

delete_campaign
DestructiveIdempotent

Delete a draft, finished or aborted campaign (an A/B campaign is deleted with both variants). It can't be restored. A scheduled, queued, sending or paused campaign is refused. Needs campaign_id. Shows a preview first and deletes only with confirm: true.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "delete_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoMust be true to make the change. Leave it out first to get a preview, show it to the user, and ask them to confirm
dry_runNoShow what would be deleted without deleting
campaign_idYesCampaign ID (from list_campaigns)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description goes further: it discloses irreversibility ('It can't be restored'), that A/B campaigns lose both variants, the status-based refusal rule, and the two-step preview gating. These are real consequences an agent must know before invoking a destructive write.

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 what is deleted and what is refused before the mechanics. 'Needs campaign_id' is mildly redundant given the required field, but nothing else is padding.

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 destructive, confirm-gated mutation with no output schema, the description covers scope, refusals, irreversibility, and the confirmation flow. What the preview actually returns and any permission requirements are left unstated, which is a modest gap rather than a blocking one.

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 coverage is 100% and the confirm property already documents the preview-then-confirm protocol in detail, so the description mostly restates it. The description reinforces that campaign_id is required and that confirm: true is the gate, but it never mentions the dry_run parameter that also exists in the schema.

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?

States a specific verb and resource (delete a campaign) plus the exact statuses in scope: draft, finished, aborted. It also notes the A/B variant behavior, which no sibling tool covers, so an agent can separate it from pause_campaign, update_campaign, or duplicate_campaign at a glance.

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?

The description gives explicit when-not guidance by naming the campaign states that are refused (scheduled, queued, sending, paused) and prescribes the preview-then-confirm sequence. It stops short of naming an alternative action for those refused states, but the exclusion criteria are clear enough for correct selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Mailercloud toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources