Skip to main content
Glama
damientilman

Mailchimp MCP

list_campaigns

List Mailchimp campaigns with metadata, send stats, and filters by status or date. Returns campaign IDs for further details.

Instructions

List campaigns with metadata, send stats, and filtering by status or date.

Use to browse campaigns and discover campaign IDs. Use get_campaign_details for full settings of a single campaign. Use get_campaign_report for post-send performance metrics. Use search_campaigns to find campaigns by keyword instead of browsing.

Authenticated via API key. Subject to Mailchimp API rate limits (max 10 concurrent requests). Read-only, safe to retry.

Args: count: Number of campaigns to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count. status: Filter by status. Valid values: 'save' (draft), 'paused', 'schedule', 'sending', 'sent'. Omit to return all statuses. since_send_time: Only return campaigns sent after this datetime. ISO 8601 format (e.g. '2025-01-01T00:00:00Z'). Only applies to sent campaigns.

Returns: JSON with total_items and campaigns array. Each campaign: id, type ('regular', 'plaintext', 'absplit', 'rss', 'variate'), status, title, subject_line, preview_text, send_time (ISO 8601 or null), emails_sent, list_id, list_name.

Example: list_campaigns(count=10, status="sent") -> {"total_items": 42, "campaigns": [{"id": "abc123", "status": "sent", ...}]}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
offsetNo
statusNo
since_send_timeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, description fully discloses read-only nature, safety to retry, authentication via API key, and rate limits (max 10 concurrent requests). These are behavioral traits beyond the basic listing operation.

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 well-structured: purpose, usage guidance, authentication/behavior, parameter details, return structure, and example. No wasted sentences; every part adds essential information. Front-loaded with key purpose.

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 tool has 4 parameters and output schema exists, the description covers all necessary aspects: input parameter details, return structure with fields, example, and behavioral notes. Nothing critical is missing.

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% parameter descriptions, but description fully compensates: defines count (1-1000, default 20), offset (pagination), status (valid values with explanations), and since_send_time (ISO 8601 format, applicable to sent campaigns). Example usage further clarifies.

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 it lists campaigns with metadata and filtering by status or date. It distinguishes from siblings like get_campaign_details (full settings for single campaign), get_campaign_report (post-send performance), and search_campaigns (keyword search).

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 tells when to use this tool versus alternatives: 'Use to browse campaigns and discover campaign IDs. Use get_campaign_details for full settings of a single campaign...' Also advises on pagination: 'Use offset when total_items exceeds count.'

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