Mailchimp MCP Server

mailchimp_landing_pages_create

Create a new Mailchimp landing page using a template ID, with optional title, description, list for signups, store ID, and tracking settings.

Instructions

Create a new landing page

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": {
      "name": "<name>",
      "template_id": "<template_id>"
    },
    "name": "mailchimp_landing_pages_create"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Landing page name
`title`	No	Page title
`list_id`	No	List ID to add signups to
`store_id`	No	E-commerce store ID (optional)
`tracking`	No	Tracking settings
`description`	No	Page description
`template_id`	Yes	Template ID to use

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 2, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Create' without explaining side effects, required permissions, or what happens upon successful creation. It does not mention whether the page is automatically published or if additional steps are needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief, consisting of a single phrase that largely restates the tool name. While it is free of fluff, it is under-specified for a tool with 7 parameters and nested objects, making it more skeletal than concise.

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?

Given the tool's complexity (7 parameters, nested tracking object) and the absence of annotations and output schema, the description is markedly incomplete. It provides no information about input expectations, return values, or potential errors, leaving the agent with only the schema to understand the 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, so all 7 parameters are already documented with their meanings. The description adds no additional semantic value beyond the schema, meeting the baseline for high schema coverage.

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 verb 'Create' and the resource 'landing page', which accurately identifies the tool's function. It distinguishes from sibling tools like list, get, update, delete, publish, and unpublish, all of which operate on existing landing pages.

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 mailchimp_landing_pages_update or mailchimp_landing_pages_publish. There is no mention of prerequisites, required inputs, or the relationship to other landing page operations.

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

Deploy Server