Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Get a template

elementor_get_template
Read-onlyIdempotent

Reads a template's Elementor element tree and regenerates element IDs by default so the copied tree can be pasted into a page without colliding with existing elements.

Instructions

Read a template's element tree. By default ids are regenerated so the tree can be pasted into a page without colliding with anything already there.

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_get_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
freshIdsNoRegenerate element ids so the tree is safe to paste.
templateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and idempotentHint=true, so the safety profile is covered. The description's one extra behavior claim (ids regenerated by default) largely duplicates the freshIds schema description, and it says nothing about the returned tree's shape or size. Minor tension worth noting: with freshIds defaulting true, successive calls return differing ids, which sits oddly against idempotentHint=true, though no true contradiction is asserted.

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 short sentences, zero waste, with the core action front-loaded and the default behavior following immediately. Nothing could be cut without losing information.

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?

For a simple read-only getter with three parameters and no output schema, the description covers the action and the one non-obvious default. It leaves the return shape (an element tree of what structure) implicit, which is a modest gap given there is no output schema to fall back on.

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 67%, so most parameters are already documented in the schema; the description restates the default of freshIds rather than adding format or edge-case detail. It adds nothing about templateId (the required param) or when to supply site.

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 gives a specific verb+resource pair ("Read a template's element tree") that is clearly distinct from mutation siblings like elementor_apply_template or elementor_save_template. It does not, however, explicitly distinguish itself from elementor_list_templates or elementor_get_page_tree, which an agent might reasonably confuse it with.

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 only implied by the mention of pasting a tree into a page; there is no explicit statement of when to call this versus elementor_apply_template or elementor_export_template. No prerequisites, no exclusions, no named alternative.

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