Skip to main content
Glama

Mailchimp

by io.github.pipeworx-io

Mailchimp Get Audience

mailchimp_get_audience
Read-onlyIdempotent

Get detailed settings and stats for a specific audience. Pass the audience ID (e.g., "abc123def456"). Returns name, member count, engagement metrics, and configuration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyYesMailchimp API key
list_idYesAudience/list ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoAudience/list ID
nameNoAudience name
statsNoAudience statistics
_linksNoHAL links
contactNoContact information
modulesNoEnabled modules
visibilityNoVisibility setting
has_welcomeNoWelcome automation enabled
list_ratingNoList rating/reputation score
date_createdNoISO date when audience was created
double_optinNoDouble opt-in enabled
beamer_addressNoBeamer address
use_archive_barNoUse archive bar
campaign_defaultsNoDefault campaign settings
email_type_optionNoEmail type option enabled
subscribe_url_longNoLong subscribe URL
notify_on_subscribeNoNotification email on subscribe
permission_reminderNoPermission reminder text
subscribe_url_shortNoShort subscribe URL
marketing_permissionsNoMarketing permissions enabled
notify_on_unsubscribeNoNotification email on unsubscribe

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"
+    },
+    "beamer_address": {
+      "description": "Beamer address",
+      "type": "string"
+    },
+    "campaign_defaults": {
+      "description": "Default campaign settings",
+      "properties": {
+        "from_email": {
+          "description": "Default from email",
+          "type": "string"
+        },
+        "from_name": {
+          "description": "Default from name",
+          "type": "string"
+        },
+        "language": {
+          "description": "Default language",
+          "type": "string"
+        },
+        "subject": {
+          "description": "Default subject",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "contact": {
+      "description": "Contact information",
+      "properties": {
+        "address1": {
+          "description": "Address line 1",
+          "type": "string"
+        },
+        "address2": {
+          "description": "Address line 2",
+          "type": "string"
+        },
+        "city": {
+          "description": "City",
+          "type": "string"
+        },
+        "company": {
+          "description": "Company name",
+          "type": "string"
+        },
+        "country": {
+          "description": "Country",
+          "type": "string"
+        },
+        "phone": {
+          "description": "Phone number",
+          "type": "string"
+        },
+        "state": {
+          "description": "State/province",
+          "type": "string"
+        },
+        "zip": {
+          "description": "Postal code",
+          "type": "string"
+        }
+      },
+      "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"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-mailchimp-api-key",
+    "list_id": "abc123def456"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds value by specifying the return fields (name, member count, engagement metrics, configuration) and providing an example ID format, enhancing transparency beyond annotations.

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 two sentences, front-loading the purpose and essential info. No unnecessary words; every sentence adds value.

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

Completeness5/5

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

Given the presence of an output schema and complete annotation coverage, the description sufficiently covers what the tool does, what parameters are needed, and the nature of returned data. No gaps are evident.

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 each parameter is already described in the schema. The description adds minimal new info (only an example ID value), so it meets the baseline without significant enhancement.

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 uses a specific verb 'Get' and identifies the resource as 'detailed settings and stats for a specific audience'. It clearly distinguishes from sibling tools like mailchimp_list_audiences (which lists) and mailchimp_get_campaign (different resource).

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 does not explicitly state when to use this tool over alternatives. It implies usage for retrieving a single audience's details, but lacks direct comparison with sibling tools. There is no 'use this when...' or 'instead of...' guidance.

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