Skip to main content
Glama

list_templates

Retrieve available email templates from Mailchimp to reuse designs for campaigns, newsletters, or automated emails.

Instructions

List available email templates.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
offsetNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `list_templates` function is decorated with `@mcp.tool()` to register it as an MCP tool, and it handles fetching templates from the Mailchimp API.
    @mcp.tool()
    async def list_templates(count: int = 20, offset: int = 0) -> str:
        """List available email templates."""
        mc = get_client()
        data = await mc.get(
            "/templates",
            params={"count": min(count, 100), "offset": offset},
        )
        templates = []
        for t in data.get("templates", []):
            templates.append({
                "id": t.get("id", ""),
                "name": t.get("name", ""),
                "type": t.get("type", ""),
                "category": t.get("category", ""),
                "active": t.get("active", False),
                "created_at": t.get("date_created", ""),
            })
        return _fmt({"total_items": data.get("total_items", 0), "templates": templates})
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but only states the basic action. It doesn't mention whether this is a read-only operation, if it requires authentication, what the output format looks like, or any rate limits or constraints. For a list operation with zero annotation coverage, this is insufficient.

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, efficient sentence with zero wasted words. It's appropriately sized for a simple list operation and front-loads the core purpose without unnecessary elaboration.

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?

Given the tool's low complexity (list operation with 2 optional parameters) and the presence of an output schema (which handles return values), the description is minimally adequate. However, it lacks context about behavioral traits and usage guidelines, which are important even with an output schema, making it incomplete for optimal agent understanding.

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 no parameter information beyond what the input schema provides (count and offset with defaults). With 0% schema description coverage, the schema lacks descriptions for these parameters, but the description doesn't compensate by explaining their purpose or usage. The baseline is 3 since the schema covers the parameters structurally, but no semantic value is added.

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 resource ('available email templates'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling tools like 'get_template' or other list operations, which would require mentioning scope or filtering characteristics.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_template' or other list operations. There's no mention of prerequisites, context for usage, or comparison with sibling tools, leaving the agent without direction on appropriate selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AlexlaGuardia/mcp-mailchimp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server