Skip to main content
Glama

Mailchimp

by io.github.pipeworx-io

Mailchimp List Audiences

mailchimp_list_audiences
Read-onlyIdempotent

View all audiences in your account. Returns audience names, member counts, and engagement stats. Use mailchimp_get_audience for detailed settings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of audiences to return (default 10, max 1000)
offsetNoOffset for pagination (default 0)
_apiKeyYesMailchimp API key (ends with -dc, e.g., abc123-us21)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
listsNoArray of audiences
_linksNoHAL links
constraintsNoAPI constraints
total_itemsNoTotal number of audiences

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"
+    },
+    "constraints": {
+      "description": "API constraints",
+      "type": "object"
+    },
+    "lists": {
+      "description": "Array of audiences",
+      "items": {
+        "properties": {
+          "_links": {
+            "description": "HAL links",
+            "type": "array"
+          },
+          "beamer_address": {
+            "description": "Beamer address",
+            "type": "string"
+          },
+          "campaign_defaults": {
+            "description": "Default campaign settings",
+            "type": "object"
+          },
+          "contact": {
+            "description": "Contact information",
+            "type": "object"
+          },
+          "date_created": {
+            "description": "ISO date when audience was created",
+            "type": "string"
+          },
+          "double_optin": {
+            "description": "Double opt-in enabled",
+            "type": "boolean"
+          },
+          "email_type_option": {
+            "description": "Email type option enabled",
+            "type": "boolean"
+          },
+          "has_welcome": {
+            "description": "Welcome automation enabled",
+            "type": "boolean"
+          },
+          "id": {
+            "description": "Audience/list ID",
+            "type": "string"
+          },
+          "list_rating": {
+            "description": "List rating/reputation score",
+            "type": "number"
+          },
+          "marketing_permissions": {
+            "description": "Marketing permissions enabled",
+            "type": "boolean"
+          },
+          "modules": {
+            "description": "Enabled modules",
+            "type": "array"
+          },
+          "name": {
+            "description": "Audience name",
+            "type": "string"
+          },
+          "notify_on_subscribe": {
+            "description": "Notification email on subscribe",
+            "type": "string"
+          },
+          "notify_on_unsubscribe": {
+            "description": "Notification email on unsubscribe",
+            "type": "string"
+          },
+          "permission_reminder": {
+            "description": "Permission reminder text",
+            "type": "string"
+          },
+          "stats": {
+            "description": "Audience statistics",
+            "properties": {
+              "avg_open_rate": {
+                "description": "Average open rate",
+                "type": "number"
+              },
+              "avg_sub_rate": {
+                "description": "Average subscription rate",
+                "type": "number"
+              },
+              "avg_unsub_rate": {
+                "description": "Average unsubscription rate",
+                "type": "number"
+              },
+              "campaign_count": {
+                "description": "Campaign count",
+                "type": "number"
+              },
+              "campaign_last_sent": {
+                "description": "Last campaign send date",
+                "type": "string"
+              },
+              "cleaned_count": {
+                "description": "Cleaned/bounced count",
+                "type": "number"
+              },
+              "click_rate": {
+                "description": "Average click rate",
+                "type": "number"
+              },
+              "member_count": {
+                "description": "Total member count",
+                "type": "number"
+              },
+              "merge_field_count": {
+                "description": "Merge field count",
+                "type": "number"
+              },
+              "total_contacts": {
+                "description": "Total contacts",
+                "type": "number"
+              },
+              "unsubscribe_count": {
+                "description": "Unsubscribed count",
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "subscribe_url_long": {
+            "description": "Long subscribe URL",
+            "type": "string"
+          },
+          "subscribe_url_short": {
+            "description": "Short subscribe URL",
+            "type": "string"
+          },
+          "use_archive_bar": {
+            "description": "Use archive bar",
+            "type": "boolean"
+          },
+          "visibility": {
+            "description": "Visibility setting",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_items": {
+      "description": "Total number of audiences",
+      "type": "number"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-mailchimp-api-key"
+  },
+  {
+    "_apiKey": "your-mailchimp-api-key",
+    "count": 50,
+    "offset": 0
+  }
+]
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive. Description adds that it returns audience names, member counts, and engagement stats, providing useful behavioral context beyond annotations. No contradiction.

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?

Two sentences, front-loaded with the action, no extraneous content. Efficient and clear.

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?

Output schema exists, so description doesn't need to detail returns beyond mentioning what stats are included. Sibling differentiation present. Could add pagination hints but schema covers it. Nearly complete.

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 covers 100% of parameters with descriptions. The tool description adds no additional parameter-level information, so baseline score of 3 applies.

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?

Description clearly states it views all audiences, with verb 'view' and resource 'audiences'. It distinguishes from sibling mailchimp_get_audience by directing to that tool for detailed settings.

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

Usage Guidelines4/5

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

Explicitly mentions alternative mailchimp_get_audience for detailed settings, giving clear context for when to use this tool. Does not mention other siblings, but the purpose is focused enough.

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