Skip to main content
Glama
Sign In
Mailchimp MCP Server

Mailchimp MCP Server

by BusyBee3333
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mailchimp_campaigns_set_content

Set campaign content via HTML, plain text, template, or URL. Define what email recipients see.

Instructions

Set the content for a campaign (HTML, plain text, template, or URL)

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

Input Schema

NameRequiredDescriptionDefault
urlNoURL to import content from
htmlNoHTML content
templateNoTemplate-based content
plain_textNoPlain text content
campaign_idYesCampaign ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral details but does not. It does not mention that setting content overwrites existing content, requires a draft campaign, or that template-based content has nested requirements. The single verb 'set' implies mutation but no further transparency.

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, tightly worded sentence that front-loads the action and lists content types. There is no redundancy or filler.

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?

Despite a nested template object and no output schema, the description provides no guidance on selecting among content sources, template section usage, or expected outcomes. It is minimal and leaves operational ambiguity for a tool with multiple input branches.

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 coverage is 100% for parameters, so the baseline is 3. The description merely echoes the parameter types already documented in the schema, adding no extra semantics like mutual exclusivity or required combination behavior.

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 uses a specific verb-resource pair ('Set the content') and explicitly lists the four content types (HTML, plain text, template, URL). This clearly distinguishes it from sibling tools like get_content (which retrieves) and campaign update (which alters settings).

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 needing an existing campaign_id, using this after campaign creation, or the fact that only one content source should be specified. The description lacks any exclusions or conditional context.

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