Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by BusyBee3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailchimp_members_update

Update an existing Mailchimp list member's subscription status, merge fields, interests, language, or VIP status by providing list ID and email address.

Instructions

Update an existing 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_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
vipNoVIP status
statusNoUpdated subscription status
list_idYesList ID
languageNoUpdated language preference
interestsNoUpdated interest preferences
merge_fieldsNoUpdated merge field values
email_addressYesMember email 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, the description carries the full burden of disclosing behavior. It only states that it updates an existing member, but does not mention side effects, permission requirements, behavior for non-existent members, or what fields are updated. The lack of detail is a significant gap for a mutation tool.

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 filler. It is appropriately sized for the information it conveys, though it could be expanded for better guidance.

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?

The tool has 7 parameters including nested objects, no output schema, and no annotations. A one-sentence description is inadequate for understanding return values, error scenarios, or how to use nested fields. The large sibling set also increases the need for more contextual detail.

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%, so every parameter has at least a basic description. The tool description itself adds no parameter information, but the baseline is 3 due to full schema coverage. Parameter descriptions are minimal (e.g., 'VIP status') but sufficient for basic understanding.

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 'Update an existing list member' uses a specific verb and resource, clearly indicating a mutation on a member. It distinguishes from 'add' by stating 'existing', but it doesn't explicitly differentiate from 'add_or_update' or other member mutations like 'archive' or 'delete'.

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 siblings such as 'mailchimp_members_add', 'mailchimp_members_add_or_update', or 'mailchimp_members_archive'. The description gives no context about prerequisites or alternative scenarios.

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