Skip to main content
Glama
pauliowest

Campaign Monitor MCP

by pauliowest

get_campaign_clicks

Retrieve a paginated list of subscribers who clicked links in a specific campaign. Use campaign ID and optional pagination parameters.

Instructions

Get a paginated list of subscribers who clicked links in a campaign

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
campaign_idYesThe campaign ID
pageNoPage number
page_sizeNoNumber of results per page
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It only mentions that the output is paginated, but omits details such as authentication requirements, rate limits, error handling for invalid campaign IDs, or any side effects. This is insufficient for safe agent use.

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 sentence of 11 words, front-loaded with the verb 'Get' and the resource. Every word is meaningful, with no redundancy or extraneous information.

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?

No output schema is provided, so the description needs to explain return values. It only states 'list of subscribers who clicked links' without detailing what fields are included (e.g., subscriber email, click timestamps, link URLs). The description is vague and insufficient for a paginated list tool.

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 input schema has 100% description coverage, with each parameter clearly described (campaign_id, page, page_size). The description adds the context of 'paginated list' but does not provide any additional meaning beyond what the schema already conveys. 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 gets a paginated list of subscribers who clicked links in a campaign, specifying both the verb (Get) and the resource (subscribers who clicked links). It also mentions pagination, distinguishing it from sibling tools like get_campaign_opens or get_campaign_unsubscribes.

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?

No explicit guidance on when to use this tool versus alternatives. The purpose is implied by the name and description, but there are no when-not-to-use instructions or comparisons to sibling tools that report different campaign metrics.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pauliowest/cmon-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server