Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by BusyBee3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailchimp_reports_get_domain_performance

Retrieve top-performing email domains for a campaign to pinpoint where engagement is highest and refine your email strategy.

Instructions

Get top-performing email domains for a campaign

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": "mailchimp_reports_get_domain_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYesCampaign ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the purpose and does not mention read-only nature, authentication requirements, pagination, or return format, leaving the agent without important behavioral context.

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 a single, well-structured sentence that immediately states the tool's purpose with no filler or redundancy. It is appropriately sized and front-loaded.

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?

For a simple one-parameter read tool with no output schema, the description provides sufficient context to select and invoke it. However, it lacks explicit notes on return values or behavior, which would be helpful given the absence of 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?

The schema covers campaign_id with a basic description, and schema coverage is 100%. The tool description adds no additional parameter semantics beyond what the schema already provides, so a baseline score of 3 is appropriate.

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's function with a specific verb ('Get') and resource ('top-performing email domains for a campaign'), distinguishing it from sibling report tools like mailchimp_reports_get (general report) and mailchimp_reports_get_click_details (click-specific).

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 implies usage for domain-level performance analysis but does not explicitly state when to use it versus alternatives, nor does it mention exclusions. It would benefit from noting that it's for domain-level breakdowns within a campaign report.

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