Skip to main content
Glama

get_landing_page

Get details and tracking statistics for a specific landing page by providing the page ID.

Instructions

Get details for a specific landing page including tracking stats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The `get_landing_page` async function is the tool handler. It fetches details for a specific landing page from Mailchimp's /landing-pages/{page_id} endpoint, returning tracking stats (visits, unique visits, subscribes, clicks) and page metadata.
    @mcp.tool()
    async def get_landing_page(page_id: str) -> str:
        """Get details for a specific landing page including tracking stats."""
        mc = get_client()
        p = await mc.get(f"/landing-pages/{page_id}")
        t = p.get("tracking", {})
        return _fmt({
            "id": p.get("id", ""),
            "name": p.get("name", ""),
            "title": p.get("title", ""),
            "status": p.get("status", ""),
            "url": p.get("url", ""),
            "list_id": p.get("list_id", ""),
            "visits": t.get("visits", 0),
            "unique_visits": t.get("unique_visits", 0),
            "subscribes": t.get("subscribes", 0),
            "clicks": t.get("clicks", 0),
            "published_at": p.get("published_at", ""),
            "created_at": p.get("created_at", ""),
            "updated_at": p.get("updated_at", ""),
        })
  • The `@mcp.tool()` decorator on line 1268 registers `get_landing_page` as an MCP tool. No separate schema definition is needed; FastMCP infers the schema from the type-annotated parameters.
    async def get_landing_page(page_id: str) -> str:
Behavior3/5

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

Annotations are absent, so description carries full burden. It mentions 'details including tracking stats' but no side effects, permissions, or rate limits. As a read operation, it's safe but could add more context like the scope of stats.

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?

Single sentence, no fluff, front-loaded with action and resource.

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 output schema exists, return values are covered. But the lack of parameter explanation and usage guidelines leaves the tool incomplete for an AI agent to decide when and how to invoke.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage. The description does not explain the page_id parameter beyond implying it identifies a landing page. No format or source guidance (e.g., from list_landing_pages).

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

Purpose5/5

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

The description clearly states 'Get details for a specific landing page including tracking stats.' It uses a specific verb and resource, and distinguishes from sibling tools like list_landing_pages by focusing on a single landing page details.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when needing details of a specific landing page, but lacks explicit guidance on when to use this tool versus alternatives like list_landing_pages or other get tools. No when-not or alternative references.

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/AlexlaGuardia/mcp-mailchimp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server