Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

delete_template_folder

DestructiveIdempotent

Permanently remove a template folder; templates inside become unfiled. Requires folder ID from list_template_folders.

Instructions

Delete a template folder permanently.

Irreversible. Deleting a folder does not delete the templates inside it; they become unfiled. Use list_template_folders to discover folder IDs.

Args: folder_id: Template folder ID to delete. Obtain from list_template_folders.

Returns: JSON with status ("deleted") and folder_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": {
      "folder_id": "<folder_id>"
    },
    "name": "delete_template_folder"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
folder_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.7.1

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds that deletion is irreversible and that templates become unfiled. However, it does not clarify behavior on repeated calls (idempotency) or provide additional context like authorization requirements or rate limits.

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 well-structured with a clear purpose statement, behavioral notes, usage tip, and parameter details. It is concise without unnecessary filler, though the 'Args' and 'Returns' sections are somewhat redundant given the schema and output schema.

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?

Covers essential aspects: purpose, behavior, and usage guidance. However, lacks completeness for the 'account' parameter, error handling, and example usage. Given the simplicity of the tool (2 params, destructive operation), the description is adequate but not fully comprehensive.

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?

Schema description coverage is 0%, so the description must compensate. It only describes the required parameter 'folder_id' (obtain from list_template_folders) but omits the optional 'account' parameter entirely. This leaves a gap in understanding all parameters.

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 ('Delete a template folder permanently') and specifies the resource (template folder). It distinguishes from sibling tools like delete_template (which deletes templates inside) and update_template_folder.

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?

Provides explicit guidance: 'Irreversible' and 'Deleting a folder does not delete the templates inside them; they become unfiled.' Also suggests using list_template_folders to obtain folder IDs. However, it does not explicitly mention when not to use this tool (e.g., alternative like updating the folder).

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