Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_elementor_update_element

Update an Elementor widget's settings by its element ID. Merge new settings into any catalog-editable widget like heading, button, or image to modify content and design.

Instructions

Update an Elementor widget by element ID. Supports all catalog-editable widgets (heading, text-editor, button, image, icon-box, icon-list, raven-*).

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": {
      "page_id": "<page_id>",
      "element_id": "<element_id>",
      "settings": "<settings>"
    },
    "name": "wp_elementor_update_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYes
settingsYesWidget settings to merge — use wp_elementor_get_widget_catalog for allowed keys
element_idYesElementor element ID from wp_elementor_list_elements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

Without annotations, the description only hints at limitations (supports catalog widgets) but omits critical traits like whether settings merge or replace, side effects, or error handling for invalid element IDs.

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?

The description is extremely concise—two short sentences—and front-loads the core action with no filler or redundancy.

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

Completeness2/5

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

Despite good schema coverage, the description lacks vital context for an update tool: no explanation of merge vs. replace behavior, return values, or error states. This omission could lead to misuse.

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?

The schema already describes element_id and settings well; the tool description adds no parameter-specific details beyond listing supported widget types. For page_id, no additional guidance is provided.

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 clearly states 'Update an Elementor widget by element ID', specifying the verb (update) and resource (widget). It also lists supported widget types, distinguishing it from specialized siblings like wp_elementor_update_button.

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 description implies usage for any catalog-editable widget but does not explicitly guide when to use this general tool versus specialized ones (e.g., wp_elementor_update_button) or mention prerequisites or exclusions.

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