Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_batches

Read-only

List recent batch operations with status and progress to monitor Mailchimp automation tasks.

Instructions

List recent batch operations with status and progress.

Use get_batch_status for detailed progress on a specific batch.

Args: count: Batch operations to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and batches array. Each: id, status ('pending'/'started'/'finished'), total_operations, finished_operations, errored_operations, submitted_at, completed_at.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_batches"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
offsetNo
accountNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • addedInput schema / properties / account
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Account"
+}
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so safety profile is covered. Description adds no new behavioral traits beyond confirming it lists recent operations, but does not disclose permissions, rate limits, or side effects. Adequate but not enhanced.

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?

Description is front-loaded with purpose, includes a structured Args/Returns block, and is concise. Minor verbosity in the Returns section but overall good.

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's low complexity (list operation, 3 parameters, output schema present), the description covers purpose, parameter details, return format, and sibling guidance. No gaps for an agent to misuse the tool.

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?

Description explains count (range, default) and offset (pagination usage) but omits the account parameter entirely. With 0% schema description coverage, this leaves one parameter undocumented, though the other two are well explained.

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 lists recent batch operations with status/progress, and explicitly distinguishes itself from the sibling get_batch_status by directing users to that tool for detailed progress on a specific batch.

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 guidance on when to use this tool vs get_batch_status, and includes pagination advice with offset parameter usage.

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