Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by AlexlaGuardia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_click_report

Retrieve click details for a campaign: see which URLs were clicked and how many times. Reports per campaign ID.

Instructions

Get click details for a campaign — which URLs were clicked and how many times.

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

Input Schema

NameRequiredDescriptionDefault
campaign_idYes
countNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states the tool's purpose but omits important traits such as read-only intent, pagination behavior, rate limits, or performance considerations for large campaigns.

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 efficiently conveys the core purpose without extraneous words. It earns its place by being clear and direct.

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

Completeness3/5

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

While the description establishes the tool's purpose and the output schema exists to detail return values, it is incomplete regarding error conditions, defaults like count=20, and any limitations. It covers basic intent but lacks depth.

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?

Schema description coverage is 0%, yet the description does not explain the parameters (campaign_id and count). It fails to clarify how count limits results or how campaign_id is used, leaving the agent without needed context.

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 click details for a campaign, specifying what information is returned (which URLs and click counts). This distinguishes it from sibling tools like get_open_report or get_unsubscribe_report, which focus on different metrics.

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 such as get_campaign_report, get_open_report, or get_sent_to_report. The description lacks any conditional or exclusionary language to assist an agent in selecting the appropriate tool.

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