Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Save a template

elementor_save_template

Save a layout to the template library from an element tree or existing page—optionally copying one element—so sections can be reused across the site.

Instructions

Save a layout to the template library, either from an element tree you pass or by copying from an existing page (optionally just one element of it). Save a section once, reuse it everywhere.

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": {
      "title": "<title>"
    },
    "name": "elementor_save_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
typeNoTemplate type: container, section, page, header, footer, popup.container
titleYes
elementsNoThe element tree to save. Omit if using sourcePostId.
sourcePostIdNoCopy the layout from this page instead.
sourceElementIdNoWith sourcePostId, save only this element and its subtree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare a non-read-only, non-destructive, open-world mutation. The description adds real behavioral context beyond that: the save can originate either from a supplied element tree or from an existing page, and can be narrowed to a single element subtree. It does not say whether an existing template with the same title is overwritten, what the tool returns (e.g. new template ID), or which capability is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the core action and the sourcing alternatives. The closing tagline ("Save a section once, reuse it everywhere") is mildly promotional but does reinforce the reuse intent in few words.

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 six-parameter mutating tool with no output schema, the description covers the input-mode story adequately but leaves the result side and idempotency/overwrite behavior unexplained. It is workable but an agent would still need to guess what comes back after a successful save.

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

Parameters4/5

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

Schema coverage is 83%, so the baseline is 3, and the description earns a small bump by framing the elements/sourcePostId/sourceElementId trio as mutually exclusive sourcing modes rather than three unrelated fields. It still adds nothing about the site or type parameters, which the schema already documents.

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?

States a specific verb and resource ("Save a layout to the template library") and then distinguishes the two input modes: passing an element tree versus copying from an existing page, including the option to copy just one element. This goes well beyond restating the title, though it never names a sibling such as elementor_import_template or elementor_apply_template to disambiguate from adjacent operations.

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?

Usage is implied through the two sourcing modes and the note that a section can be saved once and reused, but there is no explicit when-to-use/when-not guidance and no routing to alternatives like import_template (from file) or duplicate_page. The agent must infer the choice from the schema rather than the prose.

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