Skip to main content
Glama
damientilman

Mailchimp MCP

send_campaign

Send a campaign immediately to all targeted recipients. Emails begin delivering within minutes.

Instructions

Send a campaign immediately to all targeted recipients. Emails begin delivering within minutes.

Use for immediate delivery. The campaign must have content set via set_campaign_content and be in 'save' (draft) status. Use schedule_campaign instead to send at a future time. Use send_test_email first to preview the email before sending to real recipients. Once sent, emails cannot be recalled.

Authenticated via API key. Subject to Mailchimp API rate limits (max 10 concurrent requests). This operation is irreversible. Respects read-only and dry-run modes.

Args: campaign_id: The campaign ID to send (e.g. 'abc123def4'). Must be in 'save' status with content set. Obtain from create_campaign or list_campaigns(status='save').

Returns: JSON with fields: status ("sent"), campaign_id. Returns error if the campaign has no content, is already sent, or is in schedule status (use unschedule_campaign first).

Example: send_campaign(campaign_id="abc123") -> {"status": "sent", "campaign_id": "abc123"}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Despite no annotations, the description covers authentication, rate limits, irreversibility, and mode respect (read-only/dry-run). It could explicitly state that the operation is not idempotent, but it's clear from context.

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 sections (purpose, guidelines, behavioral, args, returns, example). Slightly verbose but every sentence adds value.

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?

Covers prerequisites, failure conditions, return format, and edge cases (already sent, scheduled). Complements the input schema and output schema fully.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 0% coverage, but the description adds rich semantics: required status ('save'), prerequisite content, and how to obtain the ID from create_campaign or list_campaigns.

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 explicitly states the action: 'Send a campaign immediately to all targeted recipients.' It clearly distinguishes from sibling tools like schedule_campaign and send_test_email.

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?

Provides explicit conditions: 'Use for immediate delivery. The campaign must have content set via set_campaign_content and be in save (draft) status. Use schedule_campaign instead to send at a future time. Use send_test_email first to preview.' It also notes irreversibility.

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