Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

pause_rss_campaign

Pause an active RSS campaign to stop it from sending scheduled editions. Temporarily halt the campaign, then resume it later when needed.

Instructions

Pause an active RSS-driven campaign so it stops sending scheduled editions.

Use to temporarily halt an RSS campaign; resume later with resume_rss_campaign. Applies only to campaigns of type 'rss'. Use get_campaign_details to confirm the campaign type.

Args: campaign_id: RSS campaign ID to pause. Obtain from list_campaigns or search_campaigns.

Returns: JSON with the API response confirming the pause action, or an error if not 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": "pause_rss_campaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
campaign_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations indicate mutation but not destructive. Description adds that pause is temporary and reversible, stops scheduled editions, and returns confirmation or error. Provides behavioral context beyond annotations.

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?

Description is front-loaded with purpose, includes structured Args and Returns sections. Slightly wordy but no irrelevant content. Efficient overall.

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?

Covers purpose, usage, parameter, return value, and error case. References complementary tool. Could mention handling of already paused campaigns, but overall sufficient for complexity.

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 0% but description explains campaign_id parameter with source (list_campaigns or search_campaigns). However, the optional 'account' parameter is not mentioned in the Args section, leaving it unexplained. Partial compensation.

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?

Clearly states the tool pauses an active RSS-driven campaign to stop scheduled editions. Distinguishes from siblings by specifying RSS-driven, and complements resume_rss_campaign.

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

Usage Guidelines5/5

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

Explicitly says when to use (temporarily halt RSS campaign), when not (only for RSS type), and how to confirm with get_campaign_details. Also references resume_rss_campaign for later use.

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