Skip to main content
Glama
Sign In

Mailercloud

by io.github.mailercloud-com
OverviewDiscussionsAdmin

Pause Campaign (preview, then confirm)

pause_campaign
Idempotent

Pause a scheduled, queued or sending campaign so no more emails go out until it is resumed. Resuming and stopping for good are done in the panel (Campaigns > row actions). Needs campaign_id; comment is an optional pause note. Shows a preview first and pauses 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": "pause_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
commentNoOptional note saved as the pause reason, up to 100 characters
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 paused without pausing
campaign_idYesCampaign ID (from list_campaigns)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the description adds the genuinely non-obvious part: the two-step preview-then-confirm flow and the fact that a comment becomes the saved pause reason. It does not say what happens if the campaign is already paused or not in a pausable state, which is the remaining behavioral gap.

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

Conciseness5/5

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

Three sentences, front-loaded with the effect and the state constraints, then the routing note, then the required parameters and confirm flow. No sentence is redundant or out of order.

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 four-parameter mutation with no output schema and solid annotations, this covers the confirmation protocol, state preconditions and the meaning of the optional note. Only the error/edge behavior for non-pausable campaigns and what the preview contains is left implicit.

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 every parameter already carries a description, so the schema does the heavy lifting. The description restates campaign_id as required and comment as an optional note, adding little beyond the structured fields; baseline 3 is appropriate.

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 (pause) and resource (campaign) plus the eligible states (scheduled, queued, sending) and the effect (no more emails until resumed). It also distinguishes itself from the related resume/stop operations, so an agent can tell what this tool does and does not cover.

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?

Explicitly routes resume and permanent stop to the panel (Campaigns > row actions), which is real when-not-to-use guidance. It doesn't mention tool siblings like delete_campaign or update_campaign, but the exclusions it does give are the ones that matter for this operation.

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