Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Duplicate a page

elementor_duplicate_page

Copy an Elementor page, its layout, and page settings into a new independent draft with regenerated element IDs. Edit the copy safely and publish only when ready.

Instructions

Copy a page, its Elementor layout and its page settings into a new draft, regenerating every element id so the copy is independent. The usual way to iterate on a live page safely: duplicate it, edit the copy, then publish when it is right.

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_duplicate_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
slugNo
titleNoTitle for the copy. Defaults to the original plus "(copy)".
postIdYesWordPress post ID of the Elementor page, post or template.
statusNodraft

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only cover readOnly=false, destructive=false and openWorld=true. The description adds genuinely useful behaviour the annotations do not: the output is a new draft, layout and settings are copied, and element ids are regenerated so the copy is independent of the original. It stops short of saying whether the source page is untouched, what permissions are required, or what identifier the new page 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, front-loaded with what is copied and what makes the copy independent, followed by the workflow rationale. No filler and nothing that restates the tool name.

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

Completeness4/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 no output schema, the definition covers the copy semantics well, but it leaves the return value unstated (does it return the new post ID?) and does not clarify that status can be set to publish on creation rather than only later.

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 60%, so the baseline is 3. The description only reinforces the default outcome (new draft) and says nothing about slug, the allowed status values, or how the title default behaves; schema already handles title and postId, while slug and status have no description anywhere.

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 a page, its Elementor layout and its page settings into a new draft" states a specific verb and resource and names exactly what is carried over. The detail that every element id is regenerated separates it from elementor_duplicate_element and from elementor_create_page without the agent needing to open either schema.

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?

The second sentence gives a concrete usage context and workflow: duplicate, edit the copy, publish when right. That tells the agent when this tool is the right choice, but it never names an alternative or an exclusion (e.g. when to use create_page or duplicate_element instead).

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