Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Wrap an element in a container

elementor_wrap_element

Wraps an existing Elementor element in a new container in place, enabling background, padding or width constraints without rebuilding the element.

Instructions

Put a new container around an existing element, in place. Useful for adding a background, padding or width constraint around something without rebuilding it.

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

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
postIdYesWordPress post ID of the Elementor page, post or template.
elementIdYesElementor element id, as returned by elementor_get_outline.
wrapperTypeNocontainer
wrapperSettingsNoSettings for the new wrapping container.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered. The description adds value beyond that with "in place" and "without rebuilding it", signalling that the existing element is preserved rather than recreated. It stops short of stating what happens to the element's existing settings, whether its id survives, or what the call returns.

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?

Two sentences, zero waste, with the action front-loaded and the rationale second. Every clause earns its place.

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 five-parameter mutation with a nested settings object and no output schema, the description covers the what and a use case but not the outcome. It does not say whether the element keeps its id, what the new wrapper's defaults are, or what the call returns, which an agent needs before chaining a follow-up edit.

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 80%, so postId, elementId, wrapperType and site are already documented in the schema and the description adds nothing about them. The enum choice between container and section, and what wrapperSettings accepts, are left entirely to the schema.

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?

The description uses a specific verb and resource ("Put a new container around an existing element") and pins down the placement semantics with "in place" and "without rebuilding it". It does not name the closest sibling, elementor_add_container, so the add-vs-wrap distinction is left for the agent to infer, but the core action is unambiguous.

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?

One motivating scenario is given (background, padding, width constraint), which implies when the tool is appropriate, but there is no explicit when-not guidance and no named alternative such as adding a container and moving the element into it. Prerequisites like the element existing in the outline are unstated.

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