Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Update element settings

elementor_update_element
Idempotent

Update an Elementor element's settings by applying control values; merge mode preserves existing settings, while replace swaps them wholesale.

Instructions

Change an element's settings. In merge mode (the default) the keys you pass are applied over the existing settings and everything else is left alone; in replace mode the settings object is swapped wholesale, which discards any setting you do not include. Merge is almost always what you want.

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>",
      "settings": "<settings>"
    },
    "name": "elementor_update_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNomerge keeps existing settings; replace discards anything not passed.merge
siteNoConfigured site name. Omit to use the default site.
postIdYesWordPress post ID of the Elementor page, post or template.
settingsYesElementor control values keyed by control name. Call elementor_get_widget_schema for the valid keys of a widget. Responsive variants use _tablet and _mobile suffixes, e.g. padding_tablet.
elementIdYesElementor element id, as returned by elementor_get_outline.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the safety profile (not read-only, not destructive, idempotent), so the description's main added value is explaining that replace mode "swaps wholesale" and discards omitted settings — context worth having, though it overlaps heavily with the schema's own mode description. It does not mention permission requirements, CSS cache regeneration side effects, or the response shape.

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?

Two sentences, front-loaded with the action and immediately followed by the behavioral caveat; no filler. The third clause ("Merge is almost always what you want") is pragmatic advice that earns its place.

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 5-parameter mutation tool with a nested free-form settings object and no output schema, the definition covers the risky dimension (mode) adequately and the schema handles the rest. A brief note on side effects like CSS regeneration would close the remaining gap.

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% and each parameter is documented in-schema, including the merge/replace semantics and the responsive suffix convention, so the baseline is 3. The description adds the advisory weight on merge mode but no new meaning beyond what the schema already states.

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?

"Change an element's settings" gives a specific verb (change) and resource (element settings), which cleanly separates it from siblings that touch globals, page meta, or element structure (move/wrap/duplicate). It stops short of naming a sibling explicitly, so differentiation is implied by resource rather than stated.

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?

The description gives genuine selection guidance for the one real decision the caller faces: it states merge is the default and "almost always what you want," which steers an agent away from the destructive replace path. It says nothing about when to prefer batch_edit for many elements, but guidance on the mode choice is explicit and load-bearing.

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