Skip to main content
Glama
Sign In
mailchimp-mcp

mailchimp-mcp

by livemau5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

send_campaign

Immediately send an email campaign to your audience after setting its content. Get a compact confirmation or request a full response.

Instructions

Send a campaign immediately. The campaign must have content set first via update_campaign_content. Returns compact confirmation by default — set verbose=true for full response.

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

Input Schema

NameRequiredDescriptionDefault
verboseNoReturn full API response instead of compact summary (default false)
campaign_idYesCampaign ID to send

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the prerequisite (content must be set), the immediate side effect of sending, and the return behavior (compact by default, full with verbose). This gives the agent a clear picture of what to expect.

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?

Two concise sentences with no filler. The first sentence states the action, the second adds a prerequisite and return behavior. All information is front-loaded and purpose-driven.

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 2-parameter tool with no output schema and no annotations, the description covers the essential aspects: action, prerequisite, and response type. It does not fail to mention anything critical, though it could hint at error behavior if content is missing. Overall, it is complete enough for safe invocation.

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?

Schema description coverage is 100%, so the schema covers both parameters. The description repeats the verbose behavior ('compact confirmation', 'verbose=true') rather than adding new meaning, so it does not exceed the baseline for well-documented 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's function: 'Send a campaign immediately.' The verb 'send' and resource 'campaign' are specific, and the word 'immediately' distinguishes it from sibling `schedule_campaign`. It also mentions the prerequisite of setting content, reinforcing its distinct role.

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?

The description provides a clear usage context: 'Send a campaign immediately' indicates immediate action, and 'must have content set first via update_campaign_content' gives a specific prerequisite and names an alternative tool. However, it does not explicitly contrast with `schedule_campaign`, leaving some room for interpretation.

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