elementor-mcp-agent

import_elementor_template

Import a portable Elementor template JSON into a target site as a new library entry for cross-site template synchronization.

Instructions

Import a portable template JSON (output of export_elementor_template) into a target site as a new library entry. Useful for cross-site template sync.

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": {
      "portable_json": "<portable_json>"
    },
    "name": "import_elementor_template"
  }
}

Input Schema

Name	Required	Description	Default
`site_id`	No
`portable_json`	Yes
`override_title`	No

Output Schema

Name	Required	Description	Default
`new_template_id`	Yes
`title`	Yes
`type`	Yes
`url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 27, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations indicate non-destructive and non-idempotent behavior. The description clarifies the creation of a new library entry, aligning with annotations. No contradiction, and the description adds useful context about the input format.

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 concise sentences that front-load the action and purpose. No extraneous words, every sentence adds value.

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 presence of an output schema and annotations, the description adequately covers the main purpose and input. It could mention side effects or prerequisites (e.g., site_id required or not), but overall it is sufficient.

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 0%, so the description must compensate. It only explains portable_json as the output of export_elementor_template, but site_id and override_title are left undefined. This partial coverage is insufficient for a 3-parameter tool.

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 (import), the resource (portable template JSON), and the target (new library entry in a site). It explicitly links to its counterpart export_elementor_template, distinguishing it from sibling tools like apply_template_to_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 mentions 'Useful for cross-site template sync,' which gives a clear use case. It does not explicitly list when not to use or alternative tools, but the context and sibling list adequately imply the appropriate scenarios.

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