Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Duplicate an element

elementor_duplicate_element

Copies an Elementor element and its entire subtree, placing the duplicate immediately after the original with fresh IDs to repeat a styled card, column, or row.

Instructions

Copy an element and its whole subtree, placed immediately after the original, with fresh ids throughout. The quickest way to repeat a card, column or row you have already styled.

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_duplicate_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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a non-read-only but non-destructive, open-world mutation; the description goes beyond them by disclosing the copy semantics: full subtree is included, placement is immediately after the original, and ids are regenerated. What it omits is whether the new ids are returned so the agent can act on the copy, and any permission or ordering constraints.

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, with the operational semantics (subtree, placement, fresh ids) front-loaded before the use-case hint. No redundant restatement of the title or the schema.

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 simple three-parameter mutation with no nested objects, the description covers intent, scope and placement adequately. The gap is that there is no output schema, so the description should say what comes back — particularly the new element id, which an agent needs in order to style or move the duplicated element.

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%, so postId, elementId and site are already fully documented in the schema, including that elementId comes from elementor_get_outline. The description adds no parameter-level detail beyond implying an element is the target, so the baseline 3 applies.

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?

"Copy an element and its whole subtree, placed immediately after the original, with fresh ids throughout" states a precise verb (copy), resource (element), scope (whole subtree), resulting position (immediately after the original), and a key side effect (new ids). This clearly separates it from siblings such as elementor_duplicate_page or elementor_move_element without needing to open their schemas.

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 second sentence gives a concrete usage scenario (repeating a styled card, column or row), which implies when to reach for this tool. However, it offers no exclusions or named alternatives — e.g. when to use elementor_apply_template or elementor_wrap_element instead — so the agent must infer boundaries from sibling names.

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