Skip to main content
Glama
cvrt-jh

wordpress-mcp

by cvrt-jh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mcp_update_elementor_element

Update Elementor element settings by merging changes or replacing them; optionally swap widget type in place while keeping same ID, position, and parent.

Instructions

Update settings on a single Elementor element (merge by default). With widget_type, replaces the widget in place (same id, position and parent), e.g. turn a V4 placeholder into a V3 html widget; the type must be registered with Elementor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPost/page ID
siteYesSite id (see list_sites)
settingsYesSettings to merge into (or, with settings_mode replace, to become) the element's settings
element_idYesElementor element ID
widget_typeNoReplace the widget type in place (cvrt-mcp-endpoints 1.13.0+). Widgets only, not containers.
settings_modeNomerge (default) or replace: settings become the element's complete settings

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv3.4.0
    • changedInput schema / properties / settings / description
      Previous value: -"Settings to merge into the element"New value: +"Settings to merge into (or, with settings_mode replace, to become) the element's settings"
    • addedInput schema / properties / settings_mode
      Added value: +{
+  "description": "merge (default) or replace: settings become the element's complete settings",
+  "enum": [
+    "merge",
+    "replace"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / site
      Added value: +{
+  "description": "Site id (see list_sites)",
+  "type": "string"
+}
    • addedInput schema / properties / widget_type
      Added value: +{
+  "description": "Replace the widget type in place (cvrt-mcp-endpoints 1.13.0+). Widgets only, not containers.",
+  "pattern": "^[a-z0-9][a-z0-9_-]*$",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "id",
-  "element_id",
-  "settings"
-]New value: +[
+  "site",
+  "id",
+  "element_id",
+  "settings"
+]
  2. First observedv2.0.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description must carry behavioral disclosure. It discloses the merge-default behavior and that widget_type replaces the widget while preserving id, position, and parent, but omits whether the operation is destructive, requires specific permissions, or how failures are reported.

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 description is two concise sentences that front-load the core update operation and then explain the optional widget_type replacement. It is efficient, though the widget_type example could be trimmed.

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 mutation tool with no annotations and no output schema, the description covers the main settings merge/replace behavior and the in-place widget replacement use case, but leaves gaps around permissions, error handling, and whether the change is reversible.

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 all six parameters including merge/replace enum and widget_type pattern. The description adds the concrete example and the constraint that the type must be registered with Elementor, which is marginal added value.

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 states a specific verb+resource ('Update settings on a single Elementor element') and clearly distinguishes the operation via its default merge mode and optional widget_type replacement behavior, separating it from sibling get/delete tools.

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 clarifies when to use widget_type (to replace a widget in place, e.g. turning a V4 placeholder into a V3 html widget), which is helpful context. However, it does not explicitly name or exclude sibling alternatives like mcp_get_elementor_element or mcp_delete_widget, leaving some routing ambiguity.

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

Deploy Server

Other Tools