Campaign Monitor MCP Server and API by Cotlet

Create segment from campaign in Campaign Monitor

campaign_monitor_create_segment_from_campaign

Read-onlyIdempotent

Create segment from campaign in the user's own Campaign Monitor account from ChatGPT, Claude or any AI agent. Returns how to do it in Campaign Monitor step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Campaign Monitor Cloud Browser. Campaign Monitor's official API: Campaign Monitor has a full public REST API, v3.3, for lists, subscribers, segments, campaigns, reports and transactional email, and no official MCP server (checked 22 Oct 2026).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "campaign_monitor_create_segment_from_campaign"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The annotations already declare read-only, idempotent, non-destructive and closed-world, and the description adds the crucial behavioral fact that the tool 'opens nothing by itself' and only returns a screen/button/field walkthrough. That is real value beyond the annotations. Minor gap: it does not say whether the returned steps are stable or session-dependent.

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 core behavior and the hand-off to cotlet_browser_* are front-loaded, which is good. But the trailing paragraph about Campaign Monitor's REST API v3.3 and the absence of an official MCP server ('checked 22 Oct 2026') does not help an agent decide or call this tool and dilutes the message.

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 zero-parameter guidance tool with no output schema, the description covers what it returns, that it has no side effects, and what to do next. It would be complete if it mentioned any prerequisite such as an open Campaign Monitor browser session.

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?

There are zero parameters and full schema coverage, so the baseline is 4. The description correctly implies no inputs are needed; nothing further is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Create segment from campaign') and immediately discloses the important twist: it returns step-by-step instructions rather than performing the action. That distinguishes it from an execution tool, though it is not explicitly contrasted with the sibling campaign_monitor_* tools that do act.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

States the follow-up clearly ('then do it with the cotlet_browser_* tools in the user's Campaign Monitor Cloud Browser'), which tells the agent this is the planning step of a two-step flow. It does not say when to prefer cotlet_app_guide or what to do if the user has no Cloud Browser session, but the usage context is otherwise unambiguous.

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

All Campaign Monitor MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?