Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Get the full element tree

elementor_get_page_tree
Read-onlyIdempotent

Retrieve a page's complete Elementor element tree, including all settings, to inspect configuration across many elements at once for bulk audits or troubleshooting.

Instructions

Read a page's complete element tree including every setting. This is the largest thing this server returns — only call it when you need to inspect settings across many elements at once. For normal editing use elementor_get_outline plus elementor_get_element.

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_tree"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
postIdYesWordPress post ID of the Elementor page, post or template.
summaryOnlyNoReturn counts and an outline instead of the tree itself.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.4/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 adds a genuinely useful cost signal the annotations cannot convey: this is 'the largest thing this server returns,' which tells an agent to avoid it in tight contexts. It stops short of noting that summaryOnly can shrink the same call, so the payload warning is slightly incomplete.

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?

Two sentences, zero filler. The high-cost warning is front-loaded before the alternative routing, which is the right order for an agent deciding whether to pay the payload.

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, three well-documented params and full annotation coverage, the description supplies what an agent needs: purpose, cost, and the cheaper sibling path. The only miss is not connecting the summaryOnly flag to its stated preference for getting an outline instead.

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 postId, site and summaryOnly are already fully documented, and the description adds no syntax or format detail. It never mentions summaryOnly, which is the one parameter where guidance ('use this instead of a second call') would have added value beyond the schema.

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 opens with a specific verb and resource: 'Read a page's complete element tree including every setting.' The scope qualifier 'complete... including every setting' cleanly separates it from the outline and single-element readers named in the same sentence.

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?

It states an explicit usage condition ('only call it when you need to inspect settings across many elements at once') and routes the agent to named alternatives ('for normal editing use elementor_get_outline plus elementor_get_element'). Both the when and the when-not are present.

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