Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

list_landing_pages

Retrieve all landing pages from your Mailchimp account to manage and analyze your email marketing campaigns.

Instructions

List all landing pages

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Executes the tool by calling the Mailchimp service's listLandingPages method and formatting the landing pages list into a JSON string response.
    case "list_landing_pages":
      const landingPages = await service.listLandingPages();
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              landingPages.landing_pages.map((lp) => ({
                id: lp.id,
                name: lp.name,
                type: lp.type,
                created_at: lp.created_at,
              })),
              null,
              2
            ),
          },
        ],
      };
  • Tool schema definition with name, description, and empty input schema (no parameters required).
      name: "list_landing_pages",
      description: "List all landing pages",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • src/index.ts:42-46 (registration)
    Registers the tool list (including list_landing_pages) with the MCP server via getToolDefinitions.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools: getToolDefinitions(mailchimpService),
      };
    });
  • Service helper method that makes a paginated API request to Mailchimp's /landing-pages endpoint to fetch the list of landing pages.
    async listLandingPages(): Promise<{ landing_pages: MailchimpLandingPage[] }> {
      return await this.makePaginatedRequest(
        "/landing-pages",
        "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 the full burden of behavioral disclosure. It states 'List all landing pages' but doesn't mention whether this is a read-only operation, if it requires authentication, what the return format is (e.g., pagination, fields included), or any rate limits. This leaves significant gaps for an agent to understand how to use it effectively.

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 extremely concise with 'List all landing pages'—a single, front-loaded sentence that wastes no words. It efficiently communicates the core action and resource without any unnecessary elaboration, making it easy to parse quickly.

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 what 'List all' entails (e.g., pagination, sorting, fields returned) or behavioral aspects like error handling. For a tool with no structured metadata, more context is needed to guide an agent adequately.

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, and the input schema has 100% description coverage (though empty). The description doesn't need to add parameter details, so it meets the baseline expectation. No additional semantic value is required or provided, which is appropriate for a parameterless tool.

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 'List all landing pages' clearly states the verb ('List') and resource ('landing pages'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_landing_page' (singular vs. plural), leaving some ambiguity about when to use this versus retrieving a specific landing page.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'get_landing_page' (singular) and other list tools, the description lacks context on whether this is for bulk retrieval, filtering, or specific use cases, offering no explicit or implied usage instructions.

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