Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Import a template from JSON

elementor_import_template

Import a decoded Elementor template JSON payload as a new template on a site to copy layouts between sites.

Instructions

Import an Elementor template JSON payload as a new template on this site. Pass the decoded JSON object from an Elementor export or from elementor_export_template — which makes copying a layout between sites a two-call operation.

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": {
      "payload": "<payload>"
    },
    "name": "elementor_import_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
titleNoOverride the imported template's title.
payloadYesThe decoded Elementor export object, containing "content" or "elements".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that a new template is created rather than an existing one modified, which implies additive behavior, but it says nothing about permissions, name/slug collisions on import, or how the open-world reach of the operation manifests.

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 the action and its result, followed by the sourcing/workflow note. Nothing is redundant and no sentence could be removed without losing information.

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?

The schema fully documents inputs, and annotations carry the safety profile, so the description is nearly sufficient for calling the tool. However, with no output schema present, it never indicates what comes back from an import (e.g., new template ID or resolved title), which an agent may need for the follow-up call in the two-call workflow it describes.

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%, including site defaulting and title override, so the baseline is 3. The description only adds provenance for 'payload' (decoded JSON from an export or elementor_export_template) and leaves 'site' and 'title' entirely to 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?

Uses a specific verb and resource ('Import an Elementor template JSON payload') and pins the outcome ('as a new template on this site'), which distinguishes creation-by-payload from applying an existing template or saving one. It does not explicitly contrast with close siblings such as elementor_apply_template or elementor_save_template, so an agent still has to infer the boundary.

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?

Gives concrete conditions for use: pass a decoded export object, or the output of elementor_export_template, and frames the cross-site copy as a deliberate two-call operation. No exclusion guidance is given (e.g., when to prefer apply_template instead of importing a new template), so it stops short of full when/when-not coverage.

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