Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by BusyBee3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailchimp_automations_pause_email

Need to stop a specific email automation? Pause it by providing the workflow ID and email ID, temporarily halting delivery.

Instructions

Pause a specific automation email

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>",
      "email_id": "<email_id>"
    },
    "name": "mailchimp_automations_pause_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
email_idYesAutomation email ID to pause
workflow_idYesAutomation workflow ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'pause' and does not explain side effects (e.g., whether paused emails can be resumed, impact on scheduled sends, or required permissions). This is a significant gap for a mutation tool.

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 one short, front-loaded sentence with no redundant information. It communicates the core action and resource efficiently, earning a top score for conciseness.

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

Completeness2/5

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

The tool is relatively simple with two parameters and no output schema, but with zero annotations, the description must compensate. It fails to explain the operational context—what pausing an email does behaviorally, any state requirements, or how this integrates with workflow management. The description is under-specified for a complete tool understanding.

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 has 100% description coverage for both parameters (workflow_id and email_id), so the schema already documents parameter purpose. The description adds no extra semantic detail about formats, relationships, or how to obtain these IDs, which aligns with the baseline of 3 for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Pause a specific automation email' clearly states the action (pause) and the resource (a specific automation email), distinguishing it from the sibling tool mailchimp_automations_pause which pauses the entire workflow. However, it does not explicitly name the sibling or elaborate on the scope difference, so it falls short of a 5.

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?

There is no guidance on when to use this tool versus alternatives like mailchimp_automations_pause or mailchimp_automations_start_email. The description simply states the action without any context about use cases, prerequisites, or exclusions.

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