Skip to main content
Glama

Mailchimp

by io.github.pipeworx-io

Mailchimp List Campaigns

mailchimp_list_campaigns
Read-onlyIdempotent

View all email campaigns. Returns title, type (e.g., "regular", "automation"), status, and send timestamps. Use mailchimp_get_campaign for full details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of campaigns to return (default 10, max 1000)
offsetNoOffset for pagination (default 0)
statusNoFilter by status: save, paused, schedule, sending, sent
_apiKeyYesMailchimp API key

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
_linksNoHAL links
campaignsNoArray of campaigns
total_itemsNoTotal number of campaigns

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"
+    },
+    "campaigns": {
+      "description": "Array of campaigns",
+      "items": {
+        "properties": {
+          "_links": {
+            "description": "HAL links",
+            "type": "array"
+          },
+          "archive_url": {
+            "description": "Archive URL",
+            "type": "string"
+          },
+          "create_time": {
+            "description": "ISO date when campaign was created",
+            "type": "string"
+          },
+          "emails_sent": {
+            "description": "Number of emails sent",
+            "type": "number"
+          },
+          "from_name": {
+            "description": "From name",
+            "type": "string"
+          },
+          "id": {
+            "description": "Campaign ID",
+            "type": "string"
+          },
+          "list_id": {
+            "description": "Associated audience/list ID",
+            "type": "string"
+          },
+          "long_archive_url": {
+            "description": "Long archive URL",
+            "type": "string"
+          },
+          "preview_text": {
+            "description": "Preview text",
+            "type": "string"
+          },
+          "reply_to": {
+            "description": "Reply-to email",
+            "type": "string"
+          },
+          "send_time": {
+            "description": "Send time ISO date",
+            "type": "string"
+          },
+          "status": {
+            "description": "Campaign status",
+            "enum": [
+              "save",
+              "paused",
+              "schedule",
+              "sending",
+              "sent"
+            ],
+            "type": "string"
+          },
+          "subject_line": {
+            "description": "Email subject line",
+            "type": "string"
+          },
+          "template_id": {
+            "description": "Template ID",
+            "type": "number"
+          },
+          "title": {
+            "description": "Campaign title",
+            "type": "string"
+          },
+          "type": {
+            "description": "Campaign type (regular, automation, etc.)",
+            "type": "string"
+          },
+          "web_id": {
+            "description": "Web ID",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_items": {
+      "description": "Total number of campaigns",
+      "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": 25,
+    "status": "sent"
+  }
+]
  3. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint as true, so safety profile is clear. The description adds that it returns a list with specific fields, which is useful but does not mention pagination or auth behavior beyond the schema. Given annotations cover the main traits, a score of 3 is appropriate.

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 with no wasted words. Front-loaded with the core action and result. Every sentence adds value.

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?

An output schema exists, and the description covers key return fields (title, type, status, send timestamps). However, it suggests 'all' campaigns despite pagination via count/offset, which is a minor omission. Overall sufficient for a list tool with good annotations.

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 the schema already documents all parameter details. The description does not add additional parameter-level information beyond what is in the schema, so the 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?

The description uses a specific verb ('View') and identifies the resource ('all email campaigns'). It details what is returned (title, type, status, send timestamps) and explicitly distinguishes from the sibling tool 'mailchimp_get_campaign' for full details.

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

Usage Guidelines5/5

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

The description clearly states when to use this tool ('View all email campaigns') and provides an explicit alternative ('Use mailchimp_get_campaign for full details'). This gives the agent precise guidance on tool selection.

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