Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

unpublish_landing_page

Unpublish a landing page to remove it from public access. The page can be re-published later if needed.

Instructions

Take a published landing page offline. The public URL stops serving the page.

Reversible — re-publish with publish_landing_page. Use delete_landing_page for permanent removal instead.

Returns 404 error if page_id is invalid.

Args: page_id: Landing page ID to unpublish. Obtain from list_landing_pages.

Returns: JSON with status ('unpublished') and page_id on success.

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": "unpublish_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. Addedv0.5.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations are minimal but not contradicted. Description adds what happens (URL stops serving), error handling (404 for invalid page_id), and reversibility. Provides context beyond annotations.

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: purpose statement, reversibility note, error handling, then clearly labeled Args and Returns. Every sentence adds value without redundancy.

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?

Given low complexity (2 params, 1 required, output schema exists), description covers purpose, usage, parameters, error case, and return format. Complete for agent's needs.

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

Parameters4/5

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

Schema has 0% description coverage. Description explains page_id: 'Landing page ID to unpublish. Obtain from list_landing_pages.' Adds meaning beyond schema. Account parameter has no description but is optional with default null, so minor gap.

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 'Take a published landing page offline' with the specific resource (published landing page). It distinguishes from sibling tools like delete_landing_page and publish_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 states when to use this tool (to unpublish a published page) and when not to (use delete_landing_page for permanent removal). Also notes reversibility via publish_landing_page.

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