Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

list_orders

Retrieve all orders from a Mailchimp store to track purchases and manage customer transactions.

Instructions

List all orders in a store

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_idYesThe store ID

Implementation Reference

  • Tool definition and registration in getToolDefinitions, including name, description, and input schema for validation.
    {
      name: "list_orders",
      description: "List all orders in a store",
      inputSchema: {
        type: "object",
        properties: {
          store_id: {
            type: "string",
            description: "The store ID",
          },
        },
        required: ["store_id"],
      },
    },
  • The handler logic in handleToolCall that processes the tool call, invokes the service, and formats the response as JSON.
    case "list_orders":
      const orders = await service.listOrders(args.store_id);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              orders.orders.map((o) => ({
                id: o.id,
                order_total: o.order_total,
                currency_code: o.currency_code,
                financial_status: o.financial_status,
              })),
              null,
              2
            ),
          },
        ],
      };
  • Helper method in MailchimpService that performs the paginated API request to fetch orders from Mailchimp e-commerce endpoint.
    async listOrders(storeId: string): Promise<{ orders: MailchimpOrder[] }> {
      return await this.makePaginatedRequest(
        `/ecommerce/stores/${storeId}/orders`,
        "processed_at_foreign",
        "DESC"
      );
    }
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 it's a list operation, implying read-only behavior, but doesn't mention pagination, sorting, filtering beyond store_id, rate limits, authentication needs, or what the output looks like. For a list tool with zero annotation coverage, this is inadequate.

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 waste, clearly front-loading the purpose. It's appropriately sized for a simple list tool, earning full marks 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 lack of annotations and output schema, the description is incomplete. It doesn't explain return values, behavioral traits like pagination, or how it differs from siblings. For a list tool in a context with many similar tools, this leaves significant gaps for the agent.

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%, with the single parameter 'store_id' documented in the schema. The description adds no additional meaning beyond implying the store context, so it meets the baseline of 3 where the schema does the heavy lifting without extra value from the description.

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 all orders') and resource ('in a store'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from potential siblings like 'get_order' (singular) or other list tools, which would require explicit differentiation for a score of 5.

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 siblings like 'get_order' (singular) and other list tools (e.g., 'list_products'), there's no indication of context, prerequisites, or exclusions, leaving the agent to infer usage based on naming 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