Skip to main content
Glama
damientilman

Mailchimp MCP

schedule_campaign

Schedule a Mailchimp campaign draft for future delivery. Set a specific UTC time at least 15 minutes ahead to send the campaign.

Instructions

Schedule a campaign draft for sending at a specific future time.

Use to schedule delivery of a draft campaign. The campaign must have content set via set_campaign_content and be in 'save' status. Use unschedule_campaign to cancel a scheduled send. Use send_campaign instead for immediate delivery. Use send_test_email first to preview.

Args: campaign_id: The campaign ID (e.g. 'abc123def4'). Must be in 'save' status with content set. schedule_time: When to send. ISO 8601 datetime in UTC (e.g. '2025-06-15T14:00:00Z'). Must be at least 15 minutes in the future. Mailchimp rounds to the nearest quarter hour.

Returns: JSON with fields: status ("scheduled"), campaign_id, schedule_time. Returns error if campaign has no content or is not in draft status.

Example: schedule_campaign(campaign_id="abc123", schedule_time="2025-06-15T14:00:00Z") -> {"status": "scheduled", "campaign_id": "abc123", "schedule_time": "2025-06-15T14:00:00Z"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountNo
campaign_idYes
schedule_timeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations are minimal, but description adds behavioral details: required campaign state, rounding to nearest quarter hour, and error conditions beyond what annotations provide.

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?

Well-structured with args and returns sections, plus an example. Clear and efficient, though slightly long due to example; still earns its sentences.

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 sibling context and output schema presence, the description covers prerequisites, parameter details, return format, and example, making it fully adequate for agent usage.

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 has 0% coverage, so description carries the burden. It explains campaign_id and schedule_time in detail, but omits the optional 'account' parameter, leaving it undocumented.

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 tool schedules a campaign draft for future sending, and distinguishes it from siblings like send_campaign and unschedule_campaign, making the purpose specific and well-defined.

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 states when to use (for scheduled delivery), prerequisites (content set, 'save' status), and alternatives (send_campaign for immediate, unschedule_campaign to cancel, send_test_email to preview).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/damientilman/mailchimp-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server