Skip to main content
Glama
Sign In
mailchimp-mcp

mailchimp-mcp

by livemau5
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_templates

List available email templates with optional filtering by type (user or gallery) and count. Retrieve templates to use in your email campaigns.

Instructions

List available email templates.

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
typeNoFilter by template type: 'user' (yours) or 'gallery' (Mailchimp's)
countNoNumber of templates to return (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states the core action without mentioning read-only nature, filtering by type, pagination behavior, or any side effects. This is minimal and leaves important behaviors undocumented.

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 a single, focused sentence that immediately tells the reader what the tool does. There is no wasted wording, making it highly concise and front-loaded.

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

Completeness2/5

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

This is a simple list operation with no output schema and no annotations, so the description must provide context about return values and usage scenarios. It does neither, leaving the agent with only minimal functional info and no understanding of how templates relate to other tools.

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 description coverage is 100%, so the input schema fully documents both parameters (type and count). The description adds no parameter information, but the baseline of 3 applies because the schema handles all parameter semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('List') and the resource ('available email templates'), making the purpose apparent. However, it does not explicitly differentiate itself from sibling list tools like list_audiences or list_campaigns, though the resource name makes the distinction obvious.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of typical use cases (e.g., before creating a campaign) or any exclusions, leaving the agent without context for selecting this tool from its siblings.

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