Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Render page HTML

elementor_render_page
Read-onlyIdempotent

Render an Elementor page or one element to front-end HTML to verify an edit's actual output, especially for widgets that depend on dynamic data.

Instructions

Render a page — or one element of it — to HTML as the front end would. Use this to check what an edit actually produced, especially for widgets whose output depends on dynamic data.

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": {
      "postId": "<postId>"
    },
    "name": "elementor_render_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
postIdYesWordPress post ID of the Elementor page, post or template.
elementIdNoRender just this element instead of the whole page.
maxLengthNoTruncate the returned HTML at this many characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered. The description adds real context beyond them: the output is a live front-end render with dynamic data resolved, which explains why results can vary and why this differs from a stored-data read. It does not mention cost, caching or CSS regeneration side effects, keeping it at 4.

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 tight sentences with the core action first and the use case second. Nothing is padded and no sentence repeats the tool name or title.

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 read-only render tool with a fully documented four-parameter schema and no output schema, the description covers the essential question of what comes back (HTML as the front end would emit). A note on how truncation or dynamic-data failures surface would close the remaining gap.

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 100%, so every parameter is already documented in the input schema and the baseline is 3. The description only echoes the elementId behavior with 'or one element of it', adding no format or edge-case detail about postId, site, or the maxLength truncation.

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 and resource ('Render a page — or one element of it — to HTML') and states the output form ('as the front end would'), which separates it from the structural getter siblings like elementor_get_page or elementor_get_element. It stops short of naming a sibling explicitly, so the differentiation is inferred from the verb rather than spelled out.

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 states a clear use case: 'check what an edit actually produced, especially for widgets whose output depends on dynamic data.' That tells the agent when this tool beats a plain data read. It gives no explicit when-not condition or named alternative, so it lands just under the top mark.

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