AI Abilities is a Premium Addons for Elementor feature that connects AI clients such as Claude, Cursor, and Codex to your WordPress site through a built-in MCP server. Each ability is one action the connected AI can perform on your site. This doc covers one of the Discovery abilities: Get Page Structure.
Get Page Structure lets your AI client read the element tree of an Elementor page, post, or template: every container and widget, nested exactly as they are on the page, each with its element ID and a short text summary of its content.
If the Build abilities are the AI’s hands, this is its eyes. Almost every edit starts here, because updating, removing, or inserting next to an element requires knowing its ID and where it sits in the tree.
At a Glance
| Category | Discovery |
| Access | Read-only |
| Destructive | No |
| MCP tool name | premium-addons/get-page-structure |
| Available since | Premium Addons v4.11.85 |
Before You Start
This ability is part of the AI Abilities feature. If you have not set it up yet, follow the Elementor AI Abilities (MCP Tools) Tutorial first to enable the feature and connect your AI client. The ability must also be switched on under Premium Addons → MCP Config & AI Abilities, in the Discovery category:
Use Cases
Map a page before surgery. For “Replace the testimonials section on my About page”, the AI reads the structure, spots the section by its content summary, and knows exactly which container ID to remove and where to build the replacement.
Explain a page you inherited. Ask “What is actually on my homepage and how is it built?” The AI walks the tree and describes the layout in plain terms: sections, columns, and which widgets live where.
Find every instance of a widget. Prompt “Which buttons on my landing page say ‘Sign up’?” The AI scans the tree, matches the summaries, and lists the element IDs, ready for a batch update.
Good to Know
- By default each element carries a short
settings_summary, the first bit of its text content, which is usually enough to identify it. Theinclude_settingsflag switches to full settings, but that tree can be very large. - The element IDs in the tree are exactly what
premium-addons/update-element-settings,premium-addons/remove-element, and theparent_idinputs expect. - The target must be an Elementor document; for a non-Elementor post the ability returns an error pointing to
premium-addons/create-page. - The connected WordPress user must be allowed to edit the target post.
Inputs
| Parameter | Required | Description |
|---|---|---|
post_id | Yes | The page, post, or template to read. |
include_settings | No | True returns every element’s full settings instead of the short summary. Defaults to false. |
Output
| Field | Description |
|---|---|
post_id | The document that was read. |
title | Its title. |
type | The Elementor document type (wp-page, wp-post, or a template type). |
structure | The nested element tree: each node has its ID, element type, widget type for widgets, a settings summary (or full settings), and its children. |
Come & Join the Community
Feel free to join our Facebook group and subscribe to our YouTube channel to keep up with our newest features, improvements, and helpful video tutorials.
