Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Reorder child elements

elementor_reorder_children
Idempotent

Set the order of a container's direct children by listing their element IDs; omitted IDs keep their relative order at the end, so you can move one item to the front without listing everything.

Instructions

Set the order of a container's direct children by listing their ids. Ids you leave out keep their relative order at the end, so you can move one item to the front without listing everything.

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>",
      "order": "<order>"
    },
    "name": "elementor_reorder_children"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
orderYesChild element ids in their new order.
postIdYesWordPress post ID of the Elementor page, post or template.
elementIdYesElementor element id, as returned by elementor_get_outline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so safety is largely covered. The description still adds the genuinely non-obvious behavior that omitted ids are appended at the end in their relative order, which is exactly the kind of semantic an agent cannot infer from annotations. It does not say what happens with ids not belonging to the container, which keeps it below 5.

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 sentences, front-loaded with the core action and followed by the one non-obvious rule. No filler, no restatement of the title.

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?

For a simple idempotent mutation with full schema coverage and no output schema, the description covers what an agent needs to call it correctly, including the partial-order rule. A brief note on failure behavior (e.g., invalid or foreign ids) would make it complete.

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 all four parameters are already documented in the schema and the baseline is 3. The description does add meaning for `order` beyond 'Child element ids in their new order' by explaining partial-list semantics. That is a modest value-add on top of an already complete schema.

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 states a specific verb and resource: 'Set the order of a container's direct children.' That is unambiguous and an agent can tell it apart from sibling tools like elementor_add_container or elementor_duplicate_element. It does not explicitly name any sibling, but no sibling overlaps this function, so the lack of differentiation costs little.

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?

The second sentence gives a practical usage pattern — moving one item to the front without listing everything — which implies when the tool is convenient. However, it does not state prerequisites (that elementId must be a container, that ids should come from elementor_get_outline) or when to prefer elementor_batch_edit for broader restructuring, so guidance is implied rather than explicit.

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