Skip to main content
Glama

get_page

Retrieve full page details including scrape and rewrite status, SEO metrics, WordPress publish status, and featured image for a given page ID.

Instructions

Get full page details: scrape status, rewrite status, SEO data (traffic, keywords, backlinks), WordPress publish status, and featured image

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_idYesPage UUID

Implementation Reference

  • The get_page tool handler: calls client.getPage(page_id) and returns the full page details (scrape/rewrite/publish status, SEO data, featured image). Wrapped with withErrors for structured error handling.
    server.tool(
      "get_page",
      "Get full page details: scrape status, rewrite status, SEO data (traffic, keywords, backlinks), WordPress publish status, and featured image URL.",
      {
        page_id: z.string().uuid().describe("Page UUID"),
      },
      { title: "Get page", readOnlyHint: true, idempotentHint: true, openWorldHint: true },
      withErrors(
        async ({ page_id }) => {
          const res = await client.getPage(page_id);
          return json(res.data);
        },
        "Use list_pages to find valid page IDs."
      )
    );
  • The PageData interface defines the schema returned by get_page: id, url, archive_url, title, source, top_keywords, status, is_scraped, is_rewritten, posted_to_wordpress, seo (traffic/keywords/backlinks), featured_image_url, created_at.
    export interface PageData {
      id: string;
      url: string;
      archive_url: string;
      title: string | null;
      source?: string;
      top_keywords?: string | null;
      status: string;
      is_scraped: boolean;
      is_rewritten: boolean;
      posted_to_wordpress: boolean;
      seo: {
        traffic: number | null;
        keywords: number | null;
        backlinks: number | null;
      };
      featured_image_url: string | null;
      created_at: string;
    }
  • The client.getPage method: sends GET /api/v1/pages/{id} and returns ApiResponse<PageData>. This is the underlying API call invoked by the get_page tool handler.
    async getPage(id: string): Promise<ApiResponse<PageData>> {
      return this.request("GET", `/api/v1/pages/${id}`);
  • src/tools.ts:157-171 (registration)
    The get_page tool is registered via server.tool() in the registerTools function inside src/tools.ts. It uses the MCP server's tool registration API with Zod schema for input validation.
    server.tool(
      "get_page",
      "Get full page details: scrape status, rewrite status, SEO data (traffic, keywords, backlinks), WordPress publish status, and featured image URL.",
      {
        page_id: z.string().uuid().describe("Page UUID"),
      },
      { title: "Get page", readOnlyHint: true, idempotentHint: true, openWorldHint: true },
      withErrors(
        async ({ page_id }) => {
          const res = await client.getPage(page_id);
          return json(res.data);
        },
        "Use list_pages to find valid page IDs."
      )
    );
Behavior3/5

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

No annotations provided. Description lists returned data but does not disclose behavioral traits such as idempotency, error conditions, or authentication requirements. Being a getter, read-only is implied, but not explicitly stated.

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 concise sentence with verb-first structure. Every word adds value, no redundancy. Ideal for quick scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, description lists major data groups returned. Sufficient for a simple get operation, though could mention if additional fields exist.

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?

Input schema has 100% coverage on the single parameter (page_id: UUID). Description adds no extra meaning beyond the schema's description, so baseline 3 applies.

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?

Description clearly states 'Get full page details' and enumerates specific data categories (scrape status, rewrite status, SEO data, WordPress status, featured image). This differentiates it from sibling tools like get_page_content or list_pages.

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?

No explicit when-to-use or when-not-to-use guidance given. Context implies use when full details are needed, but no alternatives or exclusions are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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/web-resurrect/mcp'

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