Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

resume_rss_campaign

Resume a paused RSS campaign to continue sending scheduled editions.

Instructions

Resume a paused RSS-driven campaign so it continues sending scheduled editions.

Use to restart an RSS campaign previously paused with pause_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 resume. Obtain from list_campaigns or search_campaigns.

Returns: JSON with the API response confirming the resume 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": "resume_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.5/5.0
Behavior4/5

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

Annotations provide no behavioral info, but description adds that resuming continues sending scheduled editions and returns a JSON confirmation or error. Could mention idempotency or side effects, but it's fairly transparent.

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?

Concise and well-structured: functional description first, then usage context, then args and returns. No fluff, sentences earn their place.

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

Completeness5/5

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

Given the simple action and presence of output schema, the description covers prerequisites (paused state, RSS type), parameter source, and return type. Complete for the tool's 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 description coverage is 0%. The description explains campaign_id well (source and purpose), but the optional account parameter is not described. Partially compensates for lack of schema descriptions.

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 verb 'Resume' and the resource 'paused RSS-driven campaign'. It distinguishes from siblings by specifying it only applies to RSS campaigns and is the counterpart to pause_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 to use for restarting an RSS campaign paused with pause_rss_campaign, notes it applies only to 'rss' type, and advises using get_campaign_details to confirm type. Provides clear context and alternatives.

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