Skip to main content
Glama

Mailchimp

by io.github.pipeworx-io

Mailchimp List Members

mailchimp_list_members
Read-onlyIdempotent

Get subscribers in an audience by ID (e.g., "abc123def456"). Returns email addresses, subscription status, and custom merge fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of members to return (default 10, max 1000)
offsetNoOffset for pagination (default 0)
statusNoFilter by status: subscribed, unsubscribed, cleaned, pending, transactional
_apiKeyYesMailchimp API key
list_idYesAudience/list ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
_linksNoHAL links
list_idNoAssociated audience/list ID
membersNoArray of audience members
total_itemsNoTotal number of members

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "_links": {
+      "description": "HAL links",
+      "type": "array"
+    },
+    "list_id": {
+      "description": "Associated audience/list ID",
+      "type": "string"
+    },
+    "members": {
+      "description": "Array of audience members",
+      "items": {
+        "properties": {
+          "_links": {
+            "description": "HAL links",
+            "type": "array"
+          },
+          "email_address": {
+            "description": "Email address",
+            "type": "string"
+          },
+          "email_client": {
+            "description": "Email client used",
+            "type": "string"
+          },
+          "email_type": {
+            "description": "Email type (html or text)",
+            "type": "string"
+          },
+          "id": {
+            "description": "Member ID",
+            "type": "string"
+          },
+          "interests": {
+            "description": "Interest category selections",
+            "type": "object"
+          },
+          "ip_opt": {
+            "description": "IP address for last opt-in",
+            "type": "string"
+          },
+          "ip_signup": {
+            "description": "IP address signup came from",
+            "type": "string"
+          },
+          "language": {
+            "description": "Language preference",
+            "type": "string"
+          },
+          "last_changed": {
+            "description": "Last changed timestamp ISO date",
+            "type": "string"
+          },
+          "last_note": {
+            "description": "Last note on member",
+            "type": "object"
+          },
+          "location": {
+            "description": "Location data",
+            "type": "object"
+          },
+          "member_rating": {
+            "description": "Member engagement rating",
+            "type": "number"
+          },
+          "merge_fields": {
+            "description": "Custom merge field values",
+            "type": "object"
+          },
+          "stats": {
+            "description": "Member engagement stats",
+            "properties": {
+              "avg_click_rate": {
+                "description": "Average click rate",
+                "type": "number"
+              },
+              "avg_open_rate": {
+                "description": "Average open rate",
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "status": {
+            "description": "Subscription status",
+            "enum": [
+              "subscribed",
+              "unsubscribed",
+              "cleaned",
+              "pending",
+              "transactional"
+            ],
+            "type": "string"
+          },
+          "timestamp_opt": {
+            "description": "Last opt-in timestamp ISO date",
+            "type": "string"
+          },
+          "timestamp_signup": {
+            "description": "Signup timestamp ISO date",
+            "type": "string"
+          },
+          "unique_email_id": {
+            "description": "Unique email ID",
+            "type": "string"
+          },
+          "vip": {
+            "description": "VIP member flag",
+            "type": "boolean"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_items": {
+      "description": "Total number of members",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-mailchimp-api-key",
+    "list_id": "abc123def456"
+  },
+  {
+    "_apiKey": "your-mailchimp-api-key",
+    "count": 100,
+    "list_id": "abc123def456",
+    "status": "subscribed"
+  }
+]
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and no destructive behavior. The description adds that it returns email, status, and merge fields but does not disclose additional behavioral traits like pagination details, rate limits, or authentication specifics beyond the API key. It is adequate given the annotations.

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 concise, using a single sentence with an embedded example. It is front-loaded with the verb and resource. No wasted words, but a second sentence could improve completeness without sacrificing brevity.

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

Completeness4/5

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

Given the rich annotations, 100% schema coverage, and existence of an output schema, the description adequately covers the core purpose and return values. It does not describe pagination or filtering in text, but those are in the schema. The tool is simple enough that the description feels complete for most use cases.

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 baseline is 3. The description reinforces the list_id parameter with an example but does not add new semantic meaning beyond the schema. The mention of return values is about output, not input parameters.

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 resource 'subscribers in an audience', provides an example ID, and specifies the returned data (email, status, merge fields). It effectively distinguishes the tool from siblings like mailchimp_get_audience and mailchimp_list_audiences.

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 does not provide any guidance on when to use this tool versus alternatives (e.g., mailchimp_get_audience for a single audience, or mailchimp_list_audiences for listing all audiences). There is no mention of prerequisites, context, or when not to use it.

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

All Mailchimp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation2/5

Several tools are near-duplicates: ask_pipeworx and ask_pipeworx_beta are currently identical, and discover_tools overlaps heavily with suggest_questions. The six Polymarket tools (bet_research, polymarket_edges, polymarket_arbitrage, etc.) have fuzzy boundaries that will mislead an agent choosing among them.

Naming Consistency3/5

Most names are snake_case, but patterns vary: verb_noun (list_subscriptions, validate_claim), adjective_noun (recent_alerts, recent_changes), bare verbs (remember, recall, forget), and domain-prefixed tools (ask_pipeworx, polymarket_*, mailchimp_*). No camelCase mixing, but the inconsistency across styles makes prediction of names harder.

Tool Count1/5

The server is named Mailchimp but only 5 of 36 tools are Mailchimp-related; the remaining 31 tools cover unrelated domains (Pipeworx data lookup, prediction markets, memory, subscriptions). This extreme mismatch means the count is wildly inappropriate for the apparent purpose.

Completeness1/5

For a Mailchimp server, the surface is severely incomplete: only read operations exist (list/get audiences, campaigns, members) with no create, update, delete, send, or automation tools. The Pipeworx tools are comparatively rich but their presence does not fix the fact that the Mailchimp domain itself is a dead end.

Resources