Skip to main content
Glama

mcp-elementor__elementor-build-composition

Destructive

SITE PARTS (Pro)

If the user asks about a header, footer, 404, single, archive, or search-results, that content lives in a SEPARATE document — not the current page. Call elementor/list-site-parts (or elementor/manage-site-parts to create) first to get the correct post_id, then invoke this tool on that id. This capability requires Elementor Pro; skip when the site-parts tools are not registered. Read [elementor://wordpress/best-practices] for repeating-layout patterns (one single template driven by dynamic data — not N duplicated pages).

RESOURCES (Read before use)

  • [elementor://wordpress/best-practices] - Opinionated WordPress patterns: repeating layouts, condition scoping, Post Content placement, dynamic tags

  • [elementor://global-classes] - Reusable CSS classes from the active kit, ordered from highest to lowest CSS priority; check FIRST before adding inline styles

  • [elementor://global-variables] - Design tokens from the active kit; use labels in CSS as var(--label) or `var(--label, fallback… Through Royally: waits for a person to approve it in Royally; nothing on the site changes until then. This connection has no undo; Royally recorded the change but cannot reverse it.

Input Schema

NameRequiredDescriptionDefault
modeNoappend (default) inserts under parent_id; replace_children removes existing direct children of parent_id first, then inserts.append
styleNoRecord mapping configuration-id → plain CSS string. Supports &:hover/&:focus/&:active nesting and @media(--breakpoint) blocks. Keys MUST match configuration-id attributes in xml_structure.
classesNoRecord mapping configuration-id → list of existing global class labels to attach to that element. Create classes first via elementor/manage-classes.
dry_runNoIf true, validate and return resolved tree without persisting.
post_idYesWordPress post ID of the document to mutate.
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)
parent_idNoID of the parent container. Omit to insert at document root.document
interactionsNoRecord mapping configuration-id → array of interaction items in the native shape. Read elementor://interactions/schema for the full shape and allowed enum values. Send [] for a configuration-id to clear its interactions.
xml_structureYesValid XML structure with custom Elementor widget tags. Every element MUST have a unique configuration-id attribute (e.g. <e-heading configuration-id="hero-title"></e-heading>). No attributes, classes, IDs, or text nodes in XML.
element_configNoRecord mapping configuration-id → plain widget settings matching elementor://widgets/schema/{type}. Keys MUST match configuration-id attributes in xml_structure. For <e-component> configuration-ids, the value is { component_id: int, overrides?: {<override_key>: <plain value>} } — see elementor/list-components.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare a destructive, non-idempotent, open-world mutation. The description adds useful context about Elementor Pro gating and a no-undo/approval note, but that note is garbled and it does not clarify what content may be overwritten or how replace_children affects existing children.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition front-loads a site-parts caveat instead of the tool's primary action, then spends significant space on resource links. The trailing Royally sentence appears truncated or disconnected, making the overall structure hard to scan.

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

Completeness2/5

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

This is a complex, destructive, ten-parameter tool with nested objects and no output schema, yet the description does not explain the composition workflow, XML-to-configuration mapping, dry-run behavior, or overwrite semantics. It provides only the site-parts prerequisite and documentation pointers.

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 ten parameters are already documented in the schema. The description adds no parameter-level meaning beyond the schema, which supports the baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never clearly states that this tool builds/composes an Elementor page from XML. It opens with site-parts routing and resource links, and the only reference to invoking the tool is 'invoke this tool on that id', which does not explain its primary action.

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

Usage Guidelines3/5

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

It gives an explicit prerequisite for header/footer/404/single/archive/search-results content and a Pro gating condition. However, it does not explain when to use this composition builder versus siblings like elementor-manage-elements or elementor-create-page, nor 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources