Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

pause_automation_email

Pause a single email in a classic Mailchimp automation workflow without stopping the entire campaign. Keep queued subscribers in place until resumed.

Instructions

Pause a specific email in a classic automation workflow.

Halts sending for a single automation email without pausing the entire workflow. Subscribers already queued remain queued until the email is started again.

Args: workflow_id: The unique id of the classic automation workflow. workflow_email_id: The unique id of the automation email to pause.

Returns: JSON confirming the pause action.

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": {
      "workflow_id": "<workflow_id>",
      "workflow_email_id": "<workflow_email_id>"
    },
    "name": "pause_automation_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
workflow_idYes
workflow_email_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.2/5.0
Behavior4/5

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

Description adds value beyond annotations by explaining the mutating action and noting that queued subscribers remain queued. No contradictions with annotations. Could mention reversibility (via start_automation_email) for completeness.

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?

Description is concise with a clear summary, behavioral details, and structured Args/Returns sections. No superfluous content.

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?

Adequately explains the tool's behavior and return type given the presence of annotations and output schema. Minor gaps: missing account parameter explanation and context on when it is valid to pause (e.g., email must be active).

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?

Args section clearly explains the two required parameters (workflow_id and workflow_email_id). However, the optional 'account' parameter is not mentioned in the description, and schema coverage is 0%, so the description should cover all parameters but does not.

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?

Description clearly states it pauses a specific email in a classic automation workflow, distinguishing it from pausing the entire workflow via the sibling pause_automation. Verb and resource are specific and unambiguous.

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 says it pauses a single email without pausing the entire workflow, providing context for when to use this over pause_automation. However, it does not mention prerequisites (e.g., workflow must be active) or explicit alternatives beyond pause_automation.

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