Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Add a widget

elementor_add_widget

Insert a new widget into an Elementor page by specifying its type and settings, then place it at the page root or inside a container or column relative to an existing element.

Instructions

Insert a new widget into a page. Pass the widget type (heading, image, button, text-editor, and so on — see elementor_list_widgets) and its settings. With no targetId the widget is appended to the page root; a widget must otherwise go inside a container or column, so use position before/after to place it beside an existing widget.

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>",
      "widgetType": "<widgetType>"
    },
    "name": "elementor_add_widget"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
postIdYesWordPress post ID of the Elementor page, post or template.
positionNoappend/prepend place the element inside the target; before/after place it as a sibling of the target.append
settingsNoElementor 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.
targetIdNoElement to place this relative to. Omit to append at the page root.
widgetTypeYesWidget type name, e.g. "heading".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the mutation profile is covered. The description adds a genuine structural constraint — widgets cannot sit at an arbitrary depth, only in a container/column — but says nothing about permission requirements, the validation of widgetType, or what happens on a bad placement. Useful but thin beyond 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.

Conciseness5/5

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

Three sentences, front-loaded with the action, then the inputs, then the placement semantics. Every sentence carries information; the pointer to elementor_list_widgets is embedded efficiently rather than given its own paragraph.

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?

This is a mutation tool with a nested settings object and no output schema, so the description carries the burden of explaining results — it never says what is returned (e.g., the new element's ID), which an agent needs to subsequently target the widget with elementor_get_element or a follow-up edit. The input side is well covered; the return/composition side is not.

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%, including enum semantics for position and the _tablet/_mobile suffix convention for settings, so the baseline is 3. The description restates targetId/position behavior already documented in the schema and adds no new parameter detail.

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?

"Insert a new widget into a page" gives a specific verb and resource, and the placement rules (root vs. container/column vs. sibling) narrow the scope nicely. It points to elementor_list_widgets for valid types, but never names elementor_add_container as the alternative for the container case it explicitly raises, so sibling differentiation is only partial.

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?

Clear operational context: omit targetId to append at the root; supply targetId plus position before/after to place beside an existing widget; consult elementor_list_widgets for types. It stops short of explicit exclusions (e.g., when to call elementor_batch_edit instead of repeated adds) but an agent knows enough to choose correctly.

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