Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Get page structure outline

elementor_get_outline
Read-onlyIdempotent

Read a compact outline of an Elementor page to get every element id, type, and label, plus the content hash needed for safe edits. Call this first before editing widgets.

Instructions

Read the structure of an Elementor page: every element id, its type, and a short label taken from its most identifying setting. This is the tool to reach for first when editing a page — it is a small fraction of the size of the full element tree and gives you the ids every other element tool needs. It also returns the content hash used for safe concurrent writes.

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

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
postIdYesWordPress post ID of the Elementor page, post or template.
maxDepthNoLevels to descend. 0 returns the whole tree; 1 returns only top-level sections.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent), but the description adds genuinely non-obvious behavior: it is far smaller than the full tree, it is a prerequisite for other element tools, and it returns a content hash for safe concurrent writes. It does not discuss truncation, error cases, or how the hash must be used, which caps it at 4.

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 tight sentences, front-loaded with what is returned, then when to use it, then the bonus content hash. Every sentence carries distinct information with no restatement of the name or schema.

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, the description must convey the return shape, and it does describe the per-element fields plus the content hash. It is slightly thin on the outline's nesting/ordering and whether the hash appears at the root only, and says nothing about the depth-limited variant's output.

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 all three parameters (site, postId, maxDepth) are already documented, making baseline 3 appropriate. The description adds no parameter-level meaning — it never mentions maxDepth's effect on the outline's shape or the site selector.

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 the structure of an Elementor page') and enumerates the payload: element id, type, and short identifying label. It also distinguishes scope against the full element tree by size, so an agent can separate it from tree/find tools without opening schemas.

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

Usage Guidelines4/5

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

Gives explicit usage context: 'the tool to reach for first when editing a page' and notes it supplies 'the ids every other element tool needs', which routes the agent correctly in edit workflows. It stops short of naming the alternative (full tree / find_elements) or stating when not to use it.

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