Get Element Schema is a WordPress ability from Ultimate Addons for Elementor — usable via Easy MCP AI, which connects Claude, ChatGPT, and any AI assistant to your site.

Install Free Plugin →

Get Element Schema

Read-only

Returns the available settings schema for a widget type, or for the section/container/column layout element type, so an AI can discover valid setting keys before building.

Requires the Ultimate Addons for Elementor (Header Footer & Elementor) plugin on WordPress 6.9+ (the WP Abilities API). No ability registers unless the plugin's 'Enable AI Tools' master switch (uae_mcp_settings.enable_abilities) is turned on in settings. Most abilities require the 'manage_options' capability; a smaller set of read/discovery abilities (template and page listing, the Elementor builder read/list/schema abilities, active-template lookup, display-rule locations, and design tokens) instead require only 'edit_posts' or 'read'. Abilities that act on a specific page, post, or template additionally check the current user's per-object 'edit_post' (or 'delete_post') capability on that item. Separately, every non-readonly (Write or Destructive) ability is gated behind a site-wide 'Allow Modifications' setting at registration time: if it is off, none of those abilities are even registered with the WP Abilities API, regardless of capability checks — this covers all template/page CRUD, widget/extension toggles, display-rule updates, theme/settings changes, and the Elementor builder writes alike, not just the builder ones. Eight of those abilities (the seven Elementor page-builder writes — build, insert-widget, update-widget, remove-element, move-element, add-section, add-column — plus pages-create) additionally re-check this same setting explicitly inside execute() as a redundant safeguard.

What it does

Given a required type ('widget', 'section', 'container', or 'column'), and (when type=widget) a widget_type slug plus an optional tab filter ('content', 'style', or 'all', default 'all'), the handler either returns the widget's schema after confirming the widget is allow-listed, or for layout types introspects Elementor's element controls directly, building a schema map of control id to {type, label, section, tab, default, options, depends_on} while skipping internal/hidden controls. It performs no writes and requires Elementor to be active for layout schema requests (500 error otherwise).

See it in action

You ask your AI assistant

"Get the content and style settings schema for the navigation-menu widget so I know what keys I can set."

Inputs

Name Type Required Description
type string Yes Type of element to get schema for: "widget", "section", "container", or "column".
widget_type string No Widget type slug, required (in practice) when type=widget, e.g. "heading", "navigation-menu".
tab string No Which settings tab to include: "content", "style", or "all" (default).

Returns

Returns type, widget_type (if applicable), title, tab, layout_mode, and a schema object mapping each setting/control key to its type, label, default, options, and toggle dependencies.

Permission

permission_callback requires current_user_can('edit_posts'). No specific post is involved, so no validate_elementor_post()/check_modifications_allowed() gating applies; only the widget allow-list check and, for layout types, an Elementor-active check.

Newsletter

The AI + WordPress space moves fast. Keep up.

New tools, workflow ideas, and product updates — be the first to know what's next.

No spam, unsubscribe anytime.