Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

delete_template

DestructiveIdempotent

Permanently delete a user-created Mailchimp template. Requires the template ID and works only for user-created templates.

Instructions

Delete a user-created template permanently.

Irreversible. Only works for user-created templates; gallery and base templates cannot be deleted. Does not affect campaigns already using this template's content. Use list_templates to find template IDs.

Returns 404 error if template_id is invalid or is not a user template.

Args: template_id: Template ID to delete (numeric string, e.g. '12345'). Must be type 'user'.

Returns: JSON with status ("deleted"), template_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": {
      "template_id": "<template_id>"
    },
    "name": "delete_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
template_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.2.2

TDQS

A4.2/5.0
Behavior4/5

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

The description adds context beyond annotations: mentions irreversibility, that it doesn't affect campaigns using the template, and returns 404 for invalid IDs. Annotations already indicate destructiveHint=true and idempotentHint=true, so the description complements well.

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?

The description is well-structured: a purpose sentence, then bullet points for behavior, followed by args and returns sections. Every sentence adds value, no fluff.

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?

Given the output schema exists, the description does not need to explain return values but includes a return format. It mentions error conditions (404). Missing explanation for the 'account' parameter slightly reduces completeness.

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?

The description adds meaning for template_id: numeric string format and requirement to be type 'user'. However, it does not mention the optional 'account' parameter at all. Schema coverage is 0%, so description should cover all params; it partially covers one.

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 'Delete a user-created template permanently.' It specifies the verb (delete) and resource (template) with a qualifier (user-created), distinguishing it from other delete tools for different resources.

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

Usage Guidelines4/5

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

The description provides clear guidance: 'Only works for user-created templates; gallery and base templates cannot be deleted.' It also advises using list_templates to find IDs. However, it does not explicitly suggest an alternative for deleting non-user templates.

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