elementor-mcp-agent

apply_template_to_page

Destructive

Apply an Elementor template or page layout to an existing draft page, with automatic backup of the target for safe rollback.

Instructions

Copy the _elementor_data + _elementor_page_settings of a SOURCE template (or page) onto a TARGET page on the same site. Backs up the target first. Use to apply a section/page template to an existing draft.

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": {
      "source_id": "<source_id>",
      "target_page_id": "<target_page_id>"
    },
    "name": "apply_template_to_page"
  }
}

Input Schema

Name	Required	Description
`site_id`	No
`source_id`	Yes	Source post id: a template or a page.
`target_page_id`	Yes
`backup_to_file`	No
`confirmation`	No

Output Schema

Name	Required	Description	Default
`mode`	Yes
`target_page_id`	Yes
`source_id`	Yes
`confirmation_token`	No
`expires_in_seconds`	No
`backup_meta_key`	No
`backup_file`	No
`css_flush`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 27, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations declare destructiveHint=true, and the description complements this by stating it backs up the target first, which is a key behavioral trait. There is no contradiction, and the description adds value beyond annotations by specifying the backup behavior.

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, no wasted words, front-loaded with the core action. Each sentence adds essential information.

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?

Given the tool complexity (5 parameters, 2 required, output schema exists), the description covers the main action and backup behavior. However, it omits details on parameters like confirmation and site_id, which are not covered by schema descriptions. Still, for a template application tool, it is nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 20%, with only source_id having a description. The tool description does not elaborate on other parameters like site_id, target_page_id, backup_to_file, or confirmation. The statement 'Backs up the target first' is ambiguous regarding whether backup_to_file controls this behavior. Parameter semantics are insufficient.

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?

The description clearly states the action: copy _elementor_data and _elementor_page_settings from a source to a target page. It specifies the resources (source template/page, target page) and the verb 'apply', which distinguishes it from sibling tools like import_elementor_template or duplicate_elementor_page.

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 description includes 'Use to apply a section/page template to an existing draft,' providing a clear use case. However, it does not explicitly mention when not to use this tool or suggest alternatives, which would strengthen guidance given the large set of sibling tools.

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