Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by BusyBee3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailchimp_campaigns_pause

Pause an active RSS campaign by providing its campaign ID to halt automated email sends and scheduled deliveries.

Instructions

Pause an RSS campaign

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": "mailchimp_campaigns_pause"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYesRSS campaign ID to pause

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention what happens when a campaign is paused (e.g., whether scheduled sends are canceled, if it is reversible, or if there are state requirements). The single word 'pause' conveys little beyond the obvious.

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?

The description is a single five-word sentence, extremely concise and front-loaded with the action. There is zero redundant information, and every word earns its place.

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

Completeness3/5

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

The tool has a simple signature with one parameter and no output schema, so the description is mostly adequate for invocation. However, it lacks behavioral context about the effects of pausing, which is important for a mutation tool. Given the simplicity, a middle score is warranted.

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?

The input schema already describes campaign_id as 'RSS campaign ID to pause', which fully covers the parameter semantics. The tool description adds no additional meaning beyond what the schema states, so the baseline score of 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?

The description clearly states the action (pause) and the resource (RSS campaign), making it easy to distinguish from sibling tools like mailchimp_campaigns_resume or mailchimp_campaigns_send. The specificity to RSS campaigns further clarifies the intended target.

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?

The description provides no guidance on when to use this tool versus alternatives such as mailchimp_campaigns_resume or mailchimp_campaigns_delete. It simply states the action without context on prerequisites, exclusions, or alternative scenarios.

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

Deploy Server

Other Tools