Skip to main content
Glama
aguaitech

Elementor MCP Server

by aguaitech

get_page

Retrieve a specific WordPress page and its Elementor metadata using the page ID for targeted content access and management.

Instructions

Retrieves a specific page from WordPress by its ID, including meta fields like _elementor_data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageIdYesThe ID of the page to retrieve.

Implementation Reference

  • The handler function for the 'get_page' tool, which retrieves page data using the getPage helper and returns it as a JSON string in the MCP content format.
    async (input) => {
      // Handler
      const pageData = await getPage(input.pageId);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(pageData),
          },
        ],
      };
    }
  • Input schema for the 'get_page' tool using Zod, validating pageId as a positive integer.
    {
      // Input Schema
      pageId: z
        .number()
        .int()
        .positive()
        .describe("The ID of the page to retrieve."),
    },
  • src/index.js:72-95 (registration)
    Full registration of the 'get_page' MCP tool using server.tool(), including name, description, input schema, and handler function.
    server.tool(
      "get_page",
      "Retrieves a specific page from WordPress by its ID, including meta fields like _elementor_data.",
      {
        // Input Schema
        pageId: z
          .number()
          .int()
          .positive()
          .describe("The ID of the page to retrieve."),
      },
      async (input) => {
        // Handler
        const pageData = await getPage(input.pageId);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(pageData),
            },
          ],
        };
      }
    );
  • Helper function getPage that performs the actual WordPress REST API GET request for a page by ID in edit context to include meta fields like _elementor_data.
    async function getPage(pageId) {
        const client = getApiClient();
        // Use context=edit to potentially get more fields like meta
        const response = await client.get(`/wp-json/wp/v2/pages/${pageId}?context=edit`);
        return response.data;
    }
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. It mentions retrieving meta fields like _elementor_data, which adds some context beyond basic retrieval. However, it lacks details on permissions, rate limits, error handling, or response format, which are important for a read operation with no output schema.

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 that front-loads the core purpose ('Retrieves a specific page from WordPress by its ID') and adds valuable detail ('including meta fields like _elementor_data'). Every word earns its place with no redundancy.

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 one parameter with full schema coverage and no output schema, the description is adequate but has gaps. It covers the purpose and includes meta fields, but without annotations or output schema, it should ideally mention more about the return data structure or behavioral aspects to be fully complete.

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 'pageId' parameter fully. The description adds no additional parameter details beyond what the schema provides, such as format examples or constraints. Baseline 3 is appropriate when the schema does the heavy lifting.

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 the specific action ('Retrieves'), resource ('a specific page from WordPress'), and key detail ('by its ID, including meta fields like _elementor_data'). It distinguishes itself from siblings like 'get_page_id_by_slug' by specifying ID-based retrieval and from 'download_page_to_file' by not downloading to a file.

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 you need to retrieve a page by ID with meta fields, but it doesn't explicitly state when to use this versus alternatives like 'get_page_id_by_slug' for slug-based lookup or 'download_page_to_file' for file output. No exclusions or prerequisites are mentioned.

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

Related 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/aguaitech/Elementor-MCP'

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