Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Get a page

elementor_get_page
Read-onlyIdempotent

Reads an Elementor page's metadata, widget census, and content hash; optionally includes the full element tree when every setting is needed.

Instructions

Read a page: metadata, a census of which widgets it uses, its content hash, and optionally the full element tree. Leave includeElements false unless you genuinely need every setting — element trees run to hundreds of kilobytes on real pages. Prefer elementor_get_outline, then elementor_get_element for the specific parts you care about.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "postId": "<postId>"
    },
    "name": "elementor_get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
postIdYesWordPress post ID of the Elementor page, post or template.
includeElementsNoInclude the complete element tree. Large; use sparingly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered. The description still adds genuine operational context beyond them: the payload can run to hundreds of kilobytes, which is the main practical risk when calling this tool. It stops short of describing pagination or truncation behavior, so it is strong but not exhaustive.

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?

Three sentences, front-loaded with the return contents, then the cost warning, then the preferred alternative path. No filler and no restatement of the title.

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

Completeness5/5

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

There is no output schema, but the description compensates by enumerating the return payload (metadata, widget census, content hash, element tree). Combined with full schema coverage and existing annotations, an agent has everything needed to decide when to call it and how to set the one optional flag.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning about includeElements beyond the schema's terse 'Large; use sparingly' — it quantifies the cost and ties it to a decision rule. It says nothing extra about site or postId, which is fine since the schema documents both adequately.

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?

States a specific verb and resource ('Read a page') and then enumerates exactly what comes back: metadata, a widget census, content hash, and optionally the full element tree. It also names the two siblings it should be chosen over ('elementor_get_outline', 'elementor_get_element'), so an agent can differentiate without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit when-not rule ('Leave includeElements false unless you genuinely need every setting') and a concrete alternative workflow ('Prefer elementor_get_outline, then elementor_get_element for the specific parts you care about'). Both the default path and the alternative path are stated, not implied.

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