Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Insert a template into a page

elementor_apply_template

Insert a saved Elementor template layout into a page with fresh element IDs, either at the root or relative to an existing element; snapshots the page first for safe edits.

Instructions

Insert a saved template's layout into a page, with fresh element ids. Place it at the page root, or relative to an existing element with targetId and position. The page is snapshotted first.

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

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
postIdYesWordPress post ID of the Elementor page, post or template.
positionNoappend/prepend place the element inside the target; before/after place it as a sibling of the target.append
targetIdNoPlace relative to this element. Omit to append at the root.
templateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, destructiveHint=false, openWorldHint=true. The description adds genuine behavioral context beyond that: element ids are regenerated (so inherited ids are not preserved) and the page is snapshotted before the mutation, which tells the agent the operation is reversible-ish and non-destructive in effect.

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 tight sentences: the action and id-regeneration come first, then placement and the snapshot note. No filler, no restated name/title.

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?

With no output schema, the description never says what comes back (new element ids? inserted-element reference?), nor what happens if postId is not an Elementor page or the template is missing. It covers the mutation and snapshot behavior adequately but leaves return/error semantics to inference for a 5-parameter write tool.

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% and the schema already spells out the position enum semantics and that omitting targetId appends at root. The description restates the targetId/position interaction rather than adding syntax, constraints, or a description for the undocumented templateId parameter, so it adds little beyond 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?

Specific verb+resource: "Insert a saved template's layout into a page, with fresh element ids." An agent can tell this apart from page-creation or element-creation tools. It does not explicitly contrast with nearby siblings such as elementor_import_template or elementor_replace_page_tree, so it stops short of a 5.

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?

It gives concrete placement guidance (root by default, or relative to an element via targetId + position), which implies when to use it. However, there is no explicit statement of when to choose this over import_template/replace_page_tree, no prerequisites, and no exclusions.

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