Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Move an element

elementor_move_element

Move an element within an Elementor page by setting referenceId and position; omit referenceId to place it at the page root. Descendant moves are refused.

Instructions

Relocate an element within the page. Give a referenceId plus a position to say where it lands; omit referenceId to move it to the page root. Moving an element into its own descendant is refused.

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>",
      "elementId": "<elementId>"
    },
    "name": "elementor_move_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
postIdYesWordPress post ID of the Elementor page, post or template.
positionNoappend/prepend place the element inside the target; before/after place it as a sibling of the target.append
elementIdYesElementor element id, as returned by elementor_get_outline.
referenceIdNoElement to position relative to. Omit to move to the page root.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world mutation, so the safety profile is covered. The description adds one genuinely useful behavioral fact — a move into the element's own descendant is refused — but says nothing about sibling ordering effects, error surfacing, or permissions, so the added context is modest.

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 compact sentences with the action first, placement rules second, and constraint last; no filler or redundant phrasing.

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

Completeness3/5

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

For a five-parameter mutation with full schema descriptions and no output schema, the definition is adequate but thin: it doesn't mention what is returned (e.g., the updated outline or moved element id) or how failures other than the descendant case are reported. An agent could call it correctly, but with less confidence about results.

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 coverage is 100%, so the schema already documents site, postId, position enum semantics, elementId, and referenceId. The description restates the referenceId-omission rule and position behavior rather than adding new meaning, which matches the baseline 3 when the schema carries the load.

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

Purpose4/5

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

The description opens with a specific verb+resource: 'Relocate an element within the page', which is clearly distinct from update (modify properties) or duplicate (copy). It doesn't explicitly name a sibling tool for contrast, keeping it just short of a 5.

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?

It gives concrete invocation context: supply referenceId plus a position to place the element relative to another element, and omit referenceId to move it to the page root. It also states one precondition (the move must not target a descendant), but offers no explicit alternatives such as wrapping or inserting a new container instead.

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