Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by BusyBee3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailchimp_automations_list

Get all classic automations (workflows) from your Mailchimp account, with optional filters for status, start time, and creation time.

Instructions

Get all automations (classic automations/workflows) in your account

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": "mailchimp_automations_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of records to return
offsetNoNumber of records to skip
statusNoFilter by status
since_start_timeNoFilter by start time (ISO 8601)
before_start_timeNoFilter by start time (ISO 8601)
since_create_timeNoFilter by creation time (ISO 8601)
before_create_timeNoFilter by creation time (ISO 8601)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It only states a read action ('Get all') but does not disclose pagination behavior, return format, or that it is a read-only operation. Minimal behavioral context.

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?

The description is a single concise sentence with no wasted words. It front-loads the action and resource clearly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 7 optional parameters, no annotations, and no output schema, the description provides minimal context. It does not explain pagination, return shape, or how filters relate to the operation. An agent would lack guidance beyond the schema.

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 description coverage is 100%, with each parameter having a descriptive label. The description adds no additional parameter detail, but the baseline is 3 given the high schema coverage.

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 verb 'Get' and the resource 'all automations', with a parenthetical clarification 'classic automations/workflows'. This distinguishes it from sibling tools like mailchimp_automations_get (singular) and actions like pause/start.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The name suggests a list operation, but the description does not explicitly note that a single automation retrieval would use mailchimp_automations_get or that specific filters might be used.

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