Skip to main content
Glama
Sign In
Mailchimp MCP

Mailchimp MCP

by damientilman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

list_templates

Read-only

Browse email templates in your Mailchimp account, including user-created and gallery templates, to retrieve template IDs and details like name and type.

Instructions

List email templates in the account (user-created and Mailchimp gallery templates).

Use to browse templates and find template IDs. Use get_template_default_content to extract HTML from a template. Use create_template to add new templates. Do not use to find campaigns; use list_campaigns instead.

Args: count: Templates to return (1-1000, default 20). offset: Pagination offset. Use when total_items exceeds count.

Returns: JSON with total_items and templates array. Each: id (int), name, type ('user'/'gallery'/ 'base'), date_created, active (boolean).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
offsetNo
accountNo

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. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so description adds value by describing return format (JSON with total_items, templates array) and fields (id, name, type, date_created, active). It also mentions it lists both user-created and gallery templates.

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?

Concise and well-structured: purpose, usage guidelines, parameter specs, return description. All sentences add value. Front-loaded with key purpose.

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 it's a list tool with read-only annotations and an output schema (mentioned), the description explains the return structure well. However, it fails to mention the 'account' parameter and doesn't specify default sorting or ordering. Still, it is largely complete.

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?

Schema coverage is 0%, so description must compensate. It describes count (1-1000, default 20) and offset (pagination). However, it omits the 'account' parameter entirely. With 3 parameters, 2 are explained, leaving a 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 it lists email templates (user-created and Mailchimp gallery). It distinguishes from sibling tools like get_template (single), get_template_default_content (extract HTML), create_template (add templates), and list_campaigns (for campaigns). Verb 'list' is specific.

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 (browse templates, find IDs), when not (for campaigns), and points to alternatives: get_template_default_content and create_template. This is full usage guidance.

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