Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

delete_connected_site

DestructiveIdempotent

Permanently remove a connected site from your Mailchimp account. Deleting it stops all associated tracking and pop-up forms.

Instructions

Delete a connected site from the account permanently.

Irreversible. After deletion, tracking and pop-up forms tied to this site stop working. Use list_connected_sites to find connected site IDs first.

Args: connected_site_id: The connected site ID to delete. Obtain from list_connected_sites.

Returns: JSON with status ("deleted"), connected_site_id.

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": {
      "connected_site_id": "<connected_site_id>"
    },
    "name": "delete_connected_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
connected_site_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate destructive and idempotent hints. Description adds specific consequences (tracking stops) and return format. No contradiction.

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?

Very concise with clear structure: action, warning, usage, args, returns. Front-loaded with purpose. No wasted words.

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

Completeness4/5

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

With annotations and output schema present, description adequately covers irreversibility, consequences, and return value. Only missing explanation for account parameter.

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

Parameters2/5

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

Only explains connected_site_id parameter. The account parameter is not mentioned despite being present in schema with no description. Schema coverage 0% requires compensation, but only partial.

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 'Delete a connected site from the account permanently.' Identifies verb and resource. Distinguishes from siblings by referencing list_connected_sites.

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 notes irreversibility, consequences for tracking and forms, and advises using list_connected_sites first. Provides clear context for when to 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