Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_campaign_unsubscribes

Read-only

Retrieve email addresses and reasons of subscribers who unsubscribed from a specific sent campaign. Analyze unsubscribe data to improve future campaigns.

Instructions

Retrieve members who unsubscribed from a specific sent campaign, with reasons.

Use get_campaign_report for aggregate unsubscribe count instead.

Returns 404 error if campaign_id is invalid. Returns empty array for unsent campaigns.

Args: campaign_id: Campaign ID (e.g. 'abc123def4'). Must be a sent campaign. count: Records to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and unsubscribes array. Each: email_address, reason (string or null), timestamp.

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": {
      "campaign_id": "<campaign_id>"
    },
    "name": "get_campaign_unsubscribes"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
offsetNo
accountNo
campaign_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • addedInput schema / properties / account
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Account"
+}
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds behavioral details beyond annotations, such as returning 404 for invalid IDs and empty arrays for unsent campaigns. It does not mention rate limits or authentication, but these are covered by the tool's annotation profile.

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 concise (around 100 words) and well-structured with clear sections: purpose, usage guidance, error cases, arguments, and return format. It is front-loaded with the primary action, making it easy to scan.

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 tool has 4 parameters, no nested objects, and an output schema exists (the description outlines the return structure), the description is largely complete. It covers error handling, pagination, and output format. The only missing element is the 'account' parameter, which may be relevant for multi-account contexts, so a slight deduction applies.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 4 parameters with 0% schema description coverage. The description compensates by explaining campaign_id (required, format), count (range 1-1000, default 20), and offset (pagination). However, the 'account' parameter is not mentioned in the description, which is a minor gap.

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 'Retrieve members who unsubscribed from a specific sent campaign, with reasons.' It uses a specific verb+resource combination and distinguishes itself from sibling tools like get_campaign_report, which provides aggregate counts.

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 explicitly advises using get_campaign_report for aggregate counts instead of this tool. It also specifies when to use it (for a specific sent campaign) and covers error cases (404 for invalid campaign_id, empty array for unsent campaigns).

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