Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Add a container or section

elementor_add_container

Insert a flexbox container, section, or column into an Elementor page and optionally seed it with child elements in one call.

Instructions

Insert a structural element — a flexbox container (the modern default), or a section/column for pages built the classic way. Containers are what you put widgets inside. You can seed it with child elements in one call.

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

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
elTypeNocontainer is the modern flexbox element; section/column are the legacy layout pair. Container is not available on every site — check containerAvailable in elementor_site_status before building a layout around it.container
postIdYesWordPress post ID of the Elementor page, post or template.
childrenNoOptional child element nodes to place inside it.
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.
targetIdNo

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 non-read-only, non-destructive, open-world behavior, so the description need not restate safety. It adds the useful fact that children can be created in the same call, but says nothing about persistence, what happens to existing layout on insert, or what identifier comes back — a real gap for a mutation tool you must chain from.

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 short sentences, front-loaded with what the tool inserts, followed by the container-vs-widget clarification and the batching hint. No filler or repeated schema material.

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 7-parameter mutation tool with nested objects and no output schema, the description covers the conceptual model but not the mechanics an agent needs: whether the new element's ID is returned for follow-up calls, and how targetId interacts with position. Adequate but leaves meaningful gaps.

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 86%, so the schema already documents elType, position, settings, and children in depth. The description only echoes the children-seeding behavior and the container-is-default point; it adds nothing for targetId, which is undocumented in 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?

Uses a specific verb ("Insert") plus a specific resource set: flexbox container, section, column. "Containers are what you put widgets inside" implicitly separates it from elementor_add_widget, but no sibling is named explicitly, so the differentiation is inferred 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?

Gives clear selection criteria between elType values: container as "the modern default," section/column for "pages built the classic way." The "seed it with child elements in one call" line signals this can replace a batch of adds. No explicit when-not-to-use case (e.g. prefer apply_template for full layouts) is given.

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