elementor-mcp-agent

read_page_elementor

Read-onlyIdempotent

Fetch a summary of a page's Elementor data structure, with an option to retrieve the full parsed tree for detailed analysis.

Instructions

Fetch a page's Elementor data structure summary. With verbose=true returns the full parsed tree (potentially MBs).

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": {
      "page_id": "<page_id>"
    },
    "name": "read_page_elementor"
  }
}

Input Schema

Name	Required	Description	Default
`site_id`	No
`page_id`	Yes
`verbose`	No

Output Schema

Name	Required	Description	Default
`page_id`	Yes
`title`	Yes
`summary`	Yes
`global_references`	Yes
`data`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 27, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The description discloses important behavioral traits beyond annotations: it warns that verbose=true returns a potentially multi-megabyte full parsed tree. This adds risk awareness. Annotations already confirm read-only, idempotent, and open-world hints, and the description aligns smoothly.

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, each earning its place: the first states the primary purpose, the second adds a critical nuance about verbosity. No redundant words, front-loaded 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?

The description is sufficient given the tool's simplicity and the presence of an output schema for return value details. It covers the two operational modes and a size warning. However, it could briefly mention that the output is a JSON structure, but that is easily inferred.

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?

The description adds meaning for the 'verbose' parameter (explaining its effect and size implications) but does not explain 'site_id' or 'page_id'. Since the input schema has 0% description coverage, the description partially compensates but leaves two parameters undocumented.

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?

Description uses a specific verb ('Fetch') and resource ('page's Elementor data structure summary'), clearly indicating what the tool does. The addition of the verbose option further clarifies the two modes. It is easily distinguishable from sibling tools like 'read_widget' or 'list_elementor_pages'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'list_elementor_pages' or 'read_widget'. There is no mention of appropriate contexts, exclusions, or prerequisites, leaving the agent to infer usage from the name alone.

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