Skip to main content
Glama
AgentX-ai

Mailchimp MCP Server

by AgentX-ai

get_landing_page

Retrieve detailed information about a specific Mailchimp landing page using its unique ID to access page content and configuration data.

Instructions

Get details of a specific landing page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesThe landing page ID

Implementation Reference

  • Handler logic for the 'get_landing_page' tool within the handleToolCall switch statement. It calls the service method and returns a formatted text response with JSON data.
    case "get_landing_page":
      const landingPage = await service.getLandingPage(args.page_id);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(landingPage, null, 2),
          },
        ],
      };
  • Tool registration in getToolDefinitions array, including name, description, and input schema.
    {
      name: "get_landing_page",
      description: "Get details of a specific landing page",
      inputSchema: {
        type: "object",
        properties: {
          page_id: {
            type: "string",
            description: "The landing page ID",
          },
        },
        required: ["page_id"],
      },
    },
  • Input schema definition for the 'get_landing_page' tool, specifying the required 'page_id' parameter.
    inputSchema: {
      type: "object",
      properties: {
        page_id: {
          type: "string",
          description: "The landing page ID",
        },
      },
      required: ["page_id"],
    },
  • Service helper method that makes the API request to fetch landing page details from Mailchimp.
    async getLandingPage(pageId: string): Promise<MailchimpLandingPage> {
      return await this.makeRequest(`/landing-pages/${pageId}`);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states 'Get details' which implies a read-only operation, but doesn't specify permissions, rate limits, error handling, or what 'details' includes. This leaves significant gaps for a tool with no annotation coverage.

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 wasted words. It's appropriately sized for a simple retrieval tool and front-loads the essential information without unnecessary elaboration.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'details' includes in the response, potential errors, or behavioral aspects like authentication needs. For a tool with rich sibling context and no structured coverage, more information is needed.

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%, so the schema already documents the single parameter 'page_id' with its description. The description doesn't add any meaning beyond what the schema provides, such as format examples or where to find page IDs. Baseline 3 is appropriate when schema does the heavy lifting.

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 'Get' and resource 'landing page' with specificity 'details of a specific landing page', making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'list_landing_pages' or other 'get_' tools, which would require explicit comparison to earn a 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. It doesn't mention sibling tools like 'list_landing_pages' for listing multiple pages or other 'get_' tools for different resources, nor does it specify prerequisites or contexts for usage.

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