Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Find elements within a page

elementor_find_elements
Read-onlyIdempotent

Search a page's Elementor elements by widget type, text in settings, or both, and return their IDs with short labels so you can locate what to edit without reading the whole tree.

Instructions

Search one page for elements by widget type, by text in their settings, or both, and get back their ids with a short label. Use this to locate what you want to edit without reading the whole tree.

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

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
textNoOnly match elements whose settings contain this text.
limitNo
postIdYesWordPress post ID of the Elementor page, post or template.
widgetTypeNoOnly match this widget or element type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and open-world, so the safety profile is covered. The description adds genuine scope info (one page, not the whole tree) and return shape (ids plus short label). However it discloses nothing about the result cap implied by the limit parameter (default 50, max 200) or about match semantics such as case sensitivity, which matters for a search tool.

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, zero filler, with the matching dimensions and the return value front-loaded before the usage hint. Nothing could be removed 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 five-parameter read-only search tool with no output schema, the description covers what it searches, how to scope it, what it returns, and when to reach for it. The remaining gap is result-set behavior (default and maximum limits causing truncation), which an agent would need to page or widen a search correctly.

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 80%, so most parameters are already documented in the schema. The phrase 'by widget type, by text in their settings, or both' adds combination semantics, making clear that widgetType and text are ANDed and either may be omitted. That is a modest gain over the schema, which describes each filter only in isolation, so the baseline 3 is 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?

States a specific verb and resource (search one page for elements) plus the matching dimensions (widget type, settings text, or both) and what comes back (ids with a short label). It implicitly contrasts with reading the full tree but never names a concrete sibling such as elementor_get_page_tree or elementor_get_outline, so it falls short of full sibling differentiation.

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?

'Use this to locate what you want to edit without reading the whole tree' gives a clear use context and implicitly points at the alternative (whole-tree reads). There are no explicit when-not conditions or named alternatives, but the usage context is unambiguous.

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