Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by BusyBee3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailchimp_members_add

Add a new member to a Mailchimp list, setting subscription status, tags, interests, and merge fields to manage your audience.

Instructions

Add a new member to 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>",
      "email_address": "<email_address>",
      "status": "<status>"
    },
    "name": "mailchimp_members_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
vipNoMark as VIP
tagsNoTags to apply to member
statusYesSubscription status
list_idYesList ID
languageNoLanguage preference (ISO 639-1)
locationNoLocation data
interestsNoInterest group preferences (e.g., {"interest_id": true})
merge_fieldsNoMerge field values (e.g., {"FNAME": "John", "LNAME": "Doe"})
email_addressYesEmail address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 only states the basic add action and does not disclose critical traits such as behavior on duplicate email addresses, idempotency, error handling, or permission requirements. Given the existence of add_or_update, the lack of clarity on duplicate handling is a significant gap.

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 redundant information. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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?

For a tool with 9 parameters, no annotations, and no output schema, the description is too minimal. It lacks essential context about when to use the tool, what happens on duplicate members, and expected outcomes, making it incomplete for reliable agent invocation.

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 provides descriptions for all 9 parameters with 100% coverage, so the baseline is 3. The description adds no additional parameter semantics beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Add a new member to a list' clearly states the action (add) and resource (member to a list). It is specific enough to distinguish from update/delete operations, but it does not explicitly differentiate from the sibling tool 'mailchimp_members_add_or_update', so it falls short of full sibling differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives like add_or_update or batch_subscribe. There is no mention of use cases, exclusions, or prerequisites, leaving the agent without context for tool selection.

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