Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

list_stores

Retrieve all e-commerce stores from your Mailchimp account to manage and analyze your connected online sales platforms.

Instructions

List all e-commerce stores

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the 'list_stores' tool in handleToolCall function. Calls service.listStores() and returns formatted JSON response with store details.
    case "list_stores":
      const stores = await service.listStores();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              stores.stores.map((s) => ({
                id: s.id,
                name: s.name,
                domain: s.domain,
                created_at: s.created_at,
              })),
              null,
              2
            ),
          },
        ],
      };
  • Tool definition including name, description, and input schema (no parameters required). Part of getToolDefinitions array used for tool registration.
    {
      name: "list_stores",
      description: "List all e-commerce stores",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • Core implementation of listStores in MailchimpService. Makes paginated API request to Mailchimp's /ecommerce/stores endpoint.
    async listStores(): Promise<{ stores: MailchimpStore[] }> {
      return await this.makePaginatedRequest(
        "/ecommerce/stores",
        "created_at",
        "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. It states the action ('List') but doesn't disclose behavioral traits like whether this is a read-only operation, if it requires authentication, how results are returned (e.g., pagination), or any rate limits. For a tool with zero annotation coverage, this is a significant gap.

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 directly states the tool's purpose with no wasted words. It's appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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 simplicity (0 parameters, no output schema), the description is minimally adequate but lacks context about behavior, alternatives, or output format. It doesn't explain what 'List' entails (e.g., returns IDs, names, full objects), which is a gap since no output schema exists to clarify.

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 0 parameters with 100% schema description coverage, so the schema fully documents the absence of inputs. The description doesn't need to add parameter details, but it could mention if there are implicit filters or scoping (e.g., 'all' implies no filtering). Baseline is 4 for zero parameters.

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 ('all e-commerce stores'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'get_store' (singular vs. plural), which could cause confusion about when to use each.

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_store' or other list_* siblings. It lacks context about prerequisites, filtering options, or any 'when-not-to-use' scenarios, leaving the agent to guess based on naming patterns alone.

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