Mailchimp MCP Server

mailchimp_members_get

Get details about a specific Mailchimp subscriber by providing list ID and email address, returning their status, profile data, and subscription info.

Instructions

Get information about a specific list member

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>",
      "email_address": "<email_address>"
    },
    "name": "mailchimp_members_get"
  }
}

Input Schema

Name	Required	Description	Default
`list_id`	Yes	List ID
`email_address`	Yes	Member email address

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

B3.4/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 the full burden. It only says 'get information' without disclosing behavior like return format, required permissions, potential errors, or that it's a read-only operation. The verb implies reading but doesn't explicitly assure safety or explain edge cases.

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, front-loaded sentence with no wasted words. It's an efficient and clear one-liner, though slightly under-specified for a full behavioral picture.

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

Completeness3/5

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

For a simple get operation with 2 well-documented parameters, the description is minimally adequate. However, with no output schema or annotations, it doesn't explain what information will be returned or what makes this different from other member getters, leaving some gaps.

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?

The schema covers 100% of parameter descriptions (list_id and email_address), so the baseline is 3. The description adds no extra meaning beyond the schema, such as clarifying that email_address must belong to the given list or that these are required.

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 'Get information about a specific list member' uses a specific verb (get) and resource (list member), making it clear this retrieves a single member's details. It distinguishes well from sibling tools like mailchimp_members_list (list all) and mailchimp_members_add/update/delete.

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 by the singular 'specific list member' but doesn't explicitly state when to use this versus alternatives, nor does it mention exclusions. It offers no guidance on choosing between this and other member-related getters like get_activity or get_goals.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server