Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

get_landing_page

Read-only

Retrieve full details of any Mailchimp landing page including description, tracking settings, and status. Requires the page ID from list_landing_pages.

Instructions

Retrieve full details of a landing page including description and tracking settings.

Use list_landing_pages to browse all pages and discover page IDs.

Returns 404 error if page_id is invalid.

Args: page_id: Landing page ID (alphanumeric string). Obtain from list_landing_pages.

Returns: JSON with id, name, title, description, status ('published'/'unpublished'/'draft'), url, published_at, created_at, updated_at, list_id, tracking.

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": {
      "page_id": "<page_id>"
    },
    "name": "get_landing_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
page_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.7.1
    • addedInput schema / properties / account
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Account"
+}
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces a read-only retrieve operation. It adds valuable context about the return format (JSON fields) and error handling (404), going beyond annotation data. However, the optional 'account' parameter is not explained.

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

Conciseness4/5

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

The description is concise and well-structured, with a clear first sentence, usage note, error note, and structured Args/Returns sections. Every part adds value, though it could be slightly more compact without losing clarity.

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

Completeness3/5

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

The tool is simple (get one page by ID) and the description covers the required parameter, return fields, and error case. However, the omission of the 'account' parameter leaves a completeness gap, especially since the tool has an output schema described in the description but no explicit schema tag.

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 0% (no descriptions in schema), so the description must compensate. It explains page_id well (alphanumeric, obtained from list_landing_pages), but completely omits the 'account' parameter, leaving its purpose unclear. This partial coverage justifies a mid-range score.

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 'Retrieve full details of a landing page' with a specific verb and resource, and distinguishes itself from siblings like list_landing_pages and create_landing_page by focusing on full details of a single 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 advises to 'Use list_landing_pages to browse all pages and discover page IDs', providing a direct pointer to a sibling tool for discovery. Also notes the 404 error condition for invalid page_id, guiding proper use.

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