Skip to main content
Glama
damientilman

Mailchimp MCP

by damientilman
OverviewSchemaRelated ServersScoreDiscussions
Python

create_batch

Submit multiple Mailchimp API operations in one asynchronous batch request. Use for bulk actions that exceed other tool limits, with each operation running independently.

Instructions

Submit multiple API operations as a single asynchronous batch request.

Use for bulk operations exceeding other tool limits (e.g. batch_subscribe max 500). Operations run asynchronously; poll with get_batch_status. Each operation runs independently. Can include destructive operations (DELETE, POST).

Authenticated via API key. Max 10 concurrent requests. Respects read-only and dry-run modes.

Args: operations: JSON array of operations. Each requires: method ('GET'/'POST'/'PATCH'/'PUT'/ 'DELETE'), path (API endpoint, e.g. '/lists/abc123/members'), optional body (JSON string).

Returns: JSON with id (batch ID for get_batch_status), status ('pending'), total_operations, submitted_at.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.9/5.0
Behavior5/5

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

Discloses behavioral traits beyond annotations (none provided): async execution, independent operations, destructive ops allowed, authentication, concurrency limit, read-only/dry-run mode. Also describes return fields.

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 paragraphs and bullet-like Args section. Informative without being verbose.

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?

Complete description for a complex async tool with no annotations and minimal schema. Covers usage, behavior, parameters, return values, and limitations.

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?

Despite 0% schema coverage, description provides detailed format for operations parameter: JSON array with method, path, optional body. Adds meaning beyond schema's bare string type.

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 'Submit multiple API operations as a single asynchronous batch request' with specific verb and resource. Differentiates from sibling batch_subscribe by noting limit of 500.

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 use case: 'Use for bulk operations exceeding other tool limits (e.g. batch_subscribe max 500)' and provides context for async polling and independent operations.

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