Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Export a template as JSON

elementor_export_template
Read-onlyIdempotent

Exports an Elementor template as JSON so it can be imported into another site through the Elementor UI or an import tool.

Instructions

Export a template in Elementor's own JSON format, ready to import into another site with elementor_import_template or through the Elementor UI.

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

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
templateIdYes

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 readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds the meaningful detail that the payload is Elementor's native JSON, but it does not say whether the JSON is returned inline, as a file path, or as a download reference, and there is no output schema to fill that gap.

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?

A single front-loaded sentence with the action first, the format second, and the consumer last. Nothing is redundant and nothing is buried.

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 only two parameters and no output schema, the definition covers the purpose and downstream use but omits the return shape, which matters for a tool whose entire product is a data payload. An agent knows what it is for but not exactly what it will receive back.

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 description coverage is only 50% and templateId — the sole required parameter — has no description anywhere. The description mentions neither templateId nor site, so it adds no meaning beyond the schema and does not compensate for the undocumented required parameter.

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?

The description names a specific verb and resource ('Export a template') plus the serialization format ('Elementor's own JSON format'), which is more than a restatement of the title. It differentiates itself from the write-side sibling ('elementor_import_template') but does not distinguish itself from retrieval siblings such as elementor_get_template or elementor_list_templates, leaving a small ambiguity about what makes an 'export' different from a 'get'.

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?

It gives a clear use case: moving a template to another site, naming both the follow-up tool (elementor_import_template) and the Elementor UI as consumers. There are no explicit exclusions and no guidance on where the templateId comes from (e.g. list_templates), so it stops short of full when/when-not guidance.

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