Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Search Elementor content site-wide

elementor_search
Read-onlyIdempotent

Search Elementor page data by text, widget type, or setting, since content stored as JSON in postmeta is invisible to normal WordPress search. Find which page holds an old phone number or element.

Instructions

Search inside Elementor page data across the site — by text, by widget type, or by which elements define a given setting. Elementor stores its content as JSON in postmeta, so it is invisible to normal WordPress search; this is the way to find "which page has that old phone number on it".

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "elementor_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
textNoText to find inside element settings.
limitNo
postIdsNoRestrict to these pages.
postTypesNoRestrict to these post types.
settingKeyNoOnly match elements that define this settings key.
widgetTypeNoOnly match this widget or element type.
caseSensitiveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.8/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 genuinely useful context beyond that: results come from JSON stored in postmeta rather than rendered content, which explains why matches may look different from what a visitor sees. It does not mention pagination or the default 100-item cap, which the schema carries instead.

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?

Two sentences, both earning their place, with the search scope front-loaded before the explanatory rationale. The parenthetical example is illustrative rather than filler. Slightly more length than strictly needed, but no wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description never indicates what a match returns (page, element, widget, matched snippet), which is significant for a search tool with 8 optional parameters. The rationale for why the tool exists is well covered, but the shape of the response is left entirely to discovery.

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 75%, so most parameters are already documented in the schema. The description adds meaning for 'text' by saying it searches 'inside element settings' and clarifies settingKey as 'elements that define a given setting', but says nothing about limit, postIds, postTypes, caseSensitive, or site, leaving the remaining gap unfilled.

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 states a specific verb and resource ('Search inside Elementor page data across the site') and enumerates the three search modes: text, widget type, and setting-defining elements. It is clear what the tool does, but it never names or contrasts itself with the closely related sibling elementor_find_elements, so an agent must infer the distinction.

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 gives a clear motivating context ('Elementor stores its content as JSON in postmeta, so it is invisible to normal WordPress search') plus a concrete scenario, 'which page has that old phone number on it', which tells the agent when this tool is the right one. It stops short of exclusions or pointing to an alternative tool for narrower element lookups.

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