Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by AlexlaGuardia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_open_report

Get details on which subscribers opened a specific campaign and the exact time they opened it, with options to control the number of results and offset.

Instructions

Get open details for a campaign — which subscribers opened and when.

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_open_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYes
countNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

The description does not disclose behavioral traits beyond the basic purpose. It omits pagination behaviors (though schema has count/offset), response structure, or any side effects. With no annotations, the description should provide more context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (one sentence) but lacks structure such as bullet points or section headings. While it avoids fluff, it could be more organized for readability.

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

Completeness2/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, the description does not need to document return values. However, it lacks usage guidance, parameter semantics, and behavioral transparency. For a tool with pagination and a required campaign ID, the description is incomplete.

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

Parameters1/5

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

The description adds no explanation for the three parameters (campaign_id, count, offset). Schema coverage is 0%, and the description fails to clarify that count/offset control pagination or that campaign_id is required. The description adds zero value beyond the raw schema.

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 tool retrieves open details for a campaign, specifying both the resource (campaign) and the data (which subscribers opened and when). It distinguishes from sibling tools like get_campaign_report and get_click_report.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., enabling open tracking) or contextual cues for selection among many sibling tools.

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