Skip to main content
Glama

mcp_get_elementor_element

Retrieve a single Elementor element's full settings, parent ID, and child IDs from a specified post or page to inspect its structure and relationships.

Instructions

Get a single Elementor element with full settings, its parent id and child ids

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": {
      "site": "<site>",
      "id": "<id>",
      "element_id": "<element_id>"
    },
    "name": "mcp_get_elementor_element"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPost/page ID
siteYesSite id (see list_sites)
element_idYesElementor element ID (hex, usually 7-8 chars)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.14.0
    • changedInput schema / properties / element_id / description
      Previous value: -"Elementor element ID (8-char hex)"New value: +"Elementor element ID (hex, usually 7-8 chars)"
    • addedInput schema / properties / element_id / pattern
      Added value: +"^[a-fA-F0-9]+$"
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "id",
      -  "element_id"
      -]New value: +[
      +  "site",
      +  "id",
      +  "element_id"
      +]
  3. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose what comes back (full settings, parent id, child ids), which is useful, but says nothing about permissions required, behavior for missing/invalid element ids, or read-only safety.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One front-loaded sentence with a leading verb and no filler. Minor ambiguity in the trailing possessive chain ('its parent id and child ids' — whose parent?), but overall efficient.

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 tool with no annotations and no output schema, the description covers what the tool fetches, its inputs' format, and its return contents. Only failure modes and the read-only nature are left implicit.

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% and each of the three parameters (site, id, element_id) has its own description including format hints, so the schema does the work. The description adds no meaning beyond it, making the baseline 3 appropriate.

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?

Specific verb+resource: 'Get a single Elementor element' with explicit scope (full settings, parent id, child ids). Clear on its own, but does not name a sibling such as mcp_get_elementor_flat or mcp_get_elementor_build to distinguish tree-vs-single retrieval.

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?

The word 'single' implies this is for retrieving one element rather than a whole page/build, and the sibling names suggest alternatives exist. However there is no explicit when-to-use/when-not-to-use statement or pointer to the alternative tool for bulk or tree retrieval.

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

Deploy Server

Other Tools