Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

delete_landing_page

DestructiveIdempotent

Permanently remove a landing page from your Mailchimp account. The page becomes inaccessible at its public URL immediately, and deletion cannot be undone.

Instructions

Permanently delete a landing page. Cannot be undone.

Side effect: the page becomes inaccessible at its public URL immediately. Past visit analytics remain in Mailchimp's reports area but the page itself is gone. Use unpublish_landing_page if you only want to take it offline temporarily.

Returns 404 error if page_id is invalid.

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

Returns: JSON with status ('deleted') 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": "delete_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.5/5.0
Behavior4/5

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

Annotations already indicate destructive and idempotent nature, but description adds specific details: immediate URL unavailability, analytics retention, return format, and 404 error handling. These go beyond annotation values.

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 clear sections, front-loaded action, and no unnecessary words. Each sentence contributes meaningful information.

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?

Covers action, side effects, error handling, return value, alternative tool, and parameter details. Output schema exists but description supplements it with usage context.

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?

Describes page_id parameter with source (list_landing_pages), adding meaning beyond schema. However, account parameter is not described. Schema coverage is 0%, so description partially compensates.

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?

Clearly states 'Permanently delete a landing page' with specific verb and resource. Distinguishes from unpublish_landing_page by contrasting permanence versus temporary offline.

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 provides when to use (permanent deletion) and when not to (use unpublish_landing_page for temporary). Includes side effects and error case, guiding agent decision-making.

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