Skip to main content
Glama
damientilman

Mailchimp MCP

create_landing_page

Create an unpublished landing page from a template to collect signups for an audience. Optionally link to an e-commerce store for tracking.

Instructions

Create a new landing page in draft status from a template, optionally linked to a store.

The page is created unpublished. Use update_landing_page to edit settings or publish_landing_page to make it live at its public URL. Use list_landing_pages or get_landing_page to inspect existing pages.

Authenticated via API key. Max 10 concurrent requests. Respects read-only and dry-run modes. Returns 400 error if template_id is invalid or list_id does not exist.

Args: name: Internal name for the page (shown in the Mailchimp dashboard, not to visitors). title: Browser tab title (shown in the page's HTML ). list_id: Audience ID this page collects signups for (e.g. 'abc123def4'). Obtain from list_audiences. template_id: Template ID to base the page on. Obtain from list_templates. store_id: Optional e-commerce store ID to link the page to. Obtain from list_ecommerce_stores. description: Optional internal description. tracking_opens: Track view-opens analytics. Default true. tracking_clicks: Track link clicks analytics. Default true.

Returns: JSON with id (use as page_id for subsequent calls), name, title, status ('unpublished'), url (null until published), created_at, list_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
titleYes
list_idYes
template_idYes
store_idNo
descriptionNo
tracking_opensNo
tracking_clicksNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Since no annotations are provided, the description fully covers behavioral traits: creation is unpublished, returns 400 on invalid IDs, supports read-only/dry-run modes. However, it could mention idempotency or duplicate behavior.

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?

Well-structured with purpose upfront, followed by usage guidance, auth/limits/errors, parameter details, and return description. No unnecessary sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no annotations or output schema, the description provides all necessary context: how to get prerequisite IDs, error handling, rate limits, and a detailed return description. It even mentions read-only/dry-run modes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description provides detailed explanations for all 8 parameters, including how to obtain prerequisite values (list_audiences, list_templates, etc.) and default behaviors for optional parameters.

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 action (create), resource (landing page), initial status (draft), source (from template), and optional link (to store). It distinguishes itself from sibling tools like publish_landing_page and update_landing_page.

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

Usage Guidelines5/5

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

Explicitly tells when to use this tool (create) and when to use alternatives (update_landing_page for edits, publish_landing_page to go live, list/get for inspection). Also mentions authentication, rate limits, and error conditions.

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/damientilman/mailchimp-mcp-server'

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