Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Get one element

elementor_get_element
Read-onlyIdempotent

Read one Elementor element and its subtree with every setting. Use it after getting the page outline to inspect only the section you plan to change.

Instructions

Read a single element and its subtree, including every setting. Use this after elementor_get_outline to inspect just the part of a page you are about to change.

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>",
      "elementId": "<elementId>"
    },
    "name": "elementor_get_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
postIdYesWordPress post ID of the Elementor page, post or template.
elementIdYesElementor element id, as returned by elementor_get_outline.
settingsOnlyNoReturn only this element's settings, not its children.

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?

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuine value beyond that by disclosing the return scope — the element's whole subtree with every setting — which matters because element trees can be large; it does not warn about payload size or how settingsOnly trims the response.

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 filler, with the capability statement front-loaded and the workflow hint second. Nothing redundant or vague enough to waste the agent's attention.

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, fully annotated read tool with 100% schema coverage and no output schema, the definition supplies what an agent needs: what is returned and when to reach for it. It could go further by noting that a full subtree with all settings can be verbose and that settingsOnly exists to limit it, but nothing critical is missing.

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 description coverage is 100% and every parameter (site, postId, elementId, settingsOnly) is documented in the schema itself. The description adds no additional meaning, such as how elementId is obtained beyond the schema's own note, so the baseline 3 applies.

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?

States a specific verb and resource: 'Read a single element and its subtree, including every setting.' That is concrete and distinguishable from elementor_get_outline (page-level overview) by the reference to a single element. It stops short of explicitly contrasting with other read tools such as elementor_find_elements or elementor_get_page_tree, so it is clear rather than sharply differentiated.

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?

Gives clear sequencing guidance: 'Use this after elementor_get_outline to inspect just the part of a page you are about to change,' which ties the tool to a read-before-edit workflow. It offers no explicit exclusions (e.g., when to prefer elementor_find_elements for locating unknown elements), so it is context-rich but not exhaustive.

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