Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by BusyBee3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailchimp_members_list

Retrieve all subscribers from a Mailchimp list. Apply filters for status, dates, email type, or VIP status, and control pagination and sorting.

Instructions

Get all members (subscribers) in a list

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "list_id": "<list_id>"
    },
    "name": "mailchimp_members_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoNumber of records to return
offsetNoNumber of records to skip
statusNoFilter by subscription status
list_idYesList ID
sort_dirNoSort direction
vip_onlyNoFilter to VIP members only
email_typeNoFilter by email type preference
sort_fieldNoSort field
since_last_changedNoFilter by last changed date (ISO 8601)
since_timestamp_optNoFilter by opt-in time (ISO 8601)
before_timestamp_optNoFilter by opt-in time (ISO 8601)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention pagination (count/offset), default filters, response format, or that 'all' members may be limited by filters. This lack of detail is a significant gap for a tool with 11 parameters.

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?

The description is a single, clear sentence with no waste. It is appropriately concise for a simple list operation, though it could be slightly more informative without losing efficiency.

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 the complexity of 11 parameters and no output schema, the description is too sparse. It fails to mention the available filters (status, vip_only, sort, date ranges) or how pagination works. The phrase 'all members' is misleading since filters and pagination can limit results.

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 coverage is 100%, with every parameter having a description, so the baseline is 3. The description adds no extra meaning beyond the schema, but the schema already explains each parameter adequately.

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 action (Get), the resource (members/subscribers), and the scope (in a list). It distinguishes itself from sibling tools like mailchimp_members_get (single member) and mailchimp_lists_list (list metadata).

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

Usage Guidelines3/5

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

The description implies usage for listing members but provides no explicit guidance on when to use it versus alternatives like mailchimp_search_members. No exclusions or alternative references are mentioned, leaving the agent to infer 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