Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

list_templates

Retrieve all email templates from your Mailchimp account for use in marketing campaigns.

Instructions

List all templates in your Mailchimp account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler for the 'list_templates' tool in the handleToolCall switch statement. It calls the Mailchimp service's listTemplates method and formats the result as MCP-compatible content with a JSON string of template summaries.
    case "list_templates":
      const templates = await service.listTemplates();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              templates.templates.map((t) => ({
                id: t.id,
                name: t.name,
                type: t.type,
                drag_and_drop: t.drag_and_drop,
                responsive: t.responsive,
                active: t.active,
                date_created: t.date_created,
              })),
              null,
              2
            ),
          },
        ],
      };
  • Tool registration entry in the tools array, defining the name, description, and input schema (no parameters required).
    {
      name: "list_templates",
      description: "List all templates in your Mailchimp account",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Input schema for the 'list_templates' tool, specifying an empty object with no required properties.
    inputSchema: {
      type: "object",
      properties: {},
      required: [],
    },
  • Helper method in MailchimpService that performs the actual API request to fetch the list of templates using a paginated endpoint.
    async listTemplates(): Promise<{ templates: MailchimpTemplate[] }> {
      return await this.makePaginatedRequest(
        "/templates",
        "date_created",
        "DESC"
      );
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'List all templates' implies a read-only operation, it doesn't address pagination behavior, rate limits, authentication requirements, or what 'all' means in practice (e.g., whether there are limits on returned items). The description is minimal and lacks operational context.

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 that states exactly what the tool does with zero wasted words. It's appropriately front-loaded with the core action and resource, making it immediately scannable and understandable.

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?

For a list operation with no annotations and no output schema, the description is insufficient. It doesn't describe the return format (e.g., array of template objects, pagination structure), error conditions, or any limitations. While the purpose is clear, the operational context needed for effective use is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and schema description coverage is 100% (empty schema). The description appropriately doesn't discuss parameters since none exist. A baseline of 4 is appropriate for parameterless tools where the schema fully documents the absence of inputs.

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 verb ('List') and resource ('templates in your Mailchimp account'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_template' (singular) or 'list_lists', but the verb+resource combination is specific enough for basic understanding.

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. With sibling tools like 'get_template' (singular retrieval) and 'list_lists' (similar pattern), there's no indication of when this list operation is appropriate versus individual retrieval or other listing operations.

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/AgentX-ai/mailchimp-mcp'

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