Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

get_list

Retrieve detailed information about a specific Mailchimp email list using its unique list ID to access audience data and configuration.

Instructions

Get details of a specific list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
list_idYesThe list ID

Implementation Reference

  • Registers the 'get_list' tool with its name, description, and input schema requiring a list_id.
    {
      name: "get_list",
      description: "Get details of a specific list",
      inputSchema: {
        type: "object",
        properties: {
          list_id: {
            type: "string",
            description: "The list ID",
          },
        },
        required: ["list_id"],
      },
    },
  • Tool handler for 'get_list': calls MailchimpService.getList with list_id argument and returns the result as formatted JSON text content.
    case "get_list":
      const list = await service.getList(args.list_id);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(list, null, 2),
          },
        ],
      };
  • Core implementation of the getList method in MailchimpService, which makes an authenticated API request to the Mailchimp /lists/{listId} endpoint.
    async getList(listId: string): Promise<MailchimpList> {
      return await this.makeRequest(`/lists/${listId}`);
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get details' which implies a read-only operation, but it doesn't specify if this requires authentication, rate limits, error handling (e.g., invalid list ID), or what the return format looks like (e.g., JSON structure). For a tool with zero annotation coverage, this is a significant gap in transparency.

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 a single, efficient sentence ('Get details of a specific list') that is front-loaded and wastes no words. It could be slightly more informative (e.g., specifying what 'details' includes), but it's appropriately sized for a simple tool, earning a high score for conciseness.

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?

Given the tool's simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It doesn't explain what 'details' means in the return value, potential errors, or how it differs from sibling tools like 'list_lists'. For a read operation with no structured output documentation, more context is needed to guide the agent effectively.

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 input schema has 1 parameter with 100% description coverage ('list_id: The list ID'), so the schema fully documents the parameter. The description adds no additional meaning beyond what the schema provides (e.g., it doesn't explain where to find the list ID or format constraints). With high schema coverage, the baseline score of 3 is appropriate.

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

Purpose3/5

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

The description 'Get details of a specific list' clearly states the verb ('Get') and resource ('list'), but it's vague about what 'details' entails (e.g., metadata, members, settings) and doesn't distinguish it from sibling tools like 'list_lists' (which likely lists multiple lists) or 'get_member' (which might retrieve list members). It's not tautological but lacks specificity.

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. It doesn't mention prerequisites (e.g., needing a list ID), exclusions, or comparisons to siblings like 'list_lists' for listing all lists or 'get_member' for list-specific member data. Usage is implied only by the name and description, with no explicit context.

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