Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Apply many element edits at once

elementor_batch_edit
Destructive

Apply multiple Elementor page edits as one atomic change: insert, update, move, duplicate, delete, reorder, or wrap elements in order; if one fails, nothing is saved.

Instructions

Run a list of element operations against a page as one atomic change: insert, update, move, duplicate, delete, reorder and wrap. Operations apply in order, each seeing the result of the last. If any one fails the whole batch is abandoned and nothing is written. Prefer this over a series of single-element calls when building or restructuring a section — it is one read and one write instead of many, and it cannot leave the page half-changed.

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>",
      "operations": "<operations>"
    },
    "name": "elementor_batch_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
labelNoSnapshot label describing this change.
postIdYesWordPress post ID of the Elementor page, post or template.
operationsYesOperations in order. Each is an object with "op" and its arguments: {"op":"insert","node":{...},"targetId":"abc","position":"append"}, {"op":"update","targetId":"abc","settings":{...},"mode":"merge"}, {"op":"move","targetId":"abc","referenceId":"def","position":"after"}, {"op":"duplicate","targetId":"abc"}, {"op":"delete","targetId":"abc"}, {"op":"reorder","targetId":"abc","order":["x","y"]}, {"op":"wrap","targetId":"abc","wrapper":{...}}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds genuinely new behavior: operations execute in order with each seeing the prior result, failure aborts the entire batch with nothing written, and it is one read plus one write. That ordering-plus-atomicity contract is exactly the information an agent needs and is not derivable from the annotations.

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

Conciseness4/5

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

The atomicity claim is front-loaded and the usage preference follows logically. Minor redundancy: 'nothing is written' and 'cannot leave the page half-changed' restate the same guarantee, making the final sentence longer than needed.

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 destructive batch mutation with no output schema, the description covers ordering, failure semantics, and cost. It does not say what the call returns on success (e.g. whether new element IDs for inserts are reported), which an agent needs to chain subsequent operations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema baseline is 3 and it already enumerates per-operation object shapes. The description adds real meaning beyond that by specifying sequential execution semantics ('each seeing the result of the last') and the all-or-nothing guarantee governing the operations array.

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

Purpose5/5

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

The description names a specific verb and resource ('run a list of element operations against a page') and enumerates the supported operation set (insert, update, move, duplicate, delete, reorder, wrap). This is clearly distinguishable from the single-element siblings such as elementor_update_element or elementor_move_element.

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 an explicit selection rule: prefer this over 'a series of single-element calls' when building or restructuring a section, with the efficiency and safety rationale. It stops short of naming specific sibling tools (e.g. elementor_update_element) or stating when NOT to batch, so it is strong guidance but not a complete routing table.

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