wordpress-mcp

mcp_search_elementor

Search all Elementor pages for specific widgets, settings, or text content by site, post type, and widget type. Filter by setting key or text to locate exact content.

Instructions

Search all Elementor pages for specific widgets, settings, or text content

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

Input Schema

Name	Required	Description	Default
`site`	Yes	Site id (see list_sites)
`setting`	No	Setting key to search in
`contains`	No	Text to search for in setting values
`per_page`	No	Max results
`post_type`	No	Limit to specific post type	any
`widget_type`	No	Filter by widget type (heading, button, image, etc.)

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv3.4.0Oct 1, 2026

addedInput schema / properties / site

Added value: +{
+  "description": "Site id (see list_sites)",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "site"
+]
```

First observedv2.0.0Jun 21, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It implies a read operation but does not state read-only semantics, what the results contain (matching pages, matching elements, counts?), how per_page/pagination behaves, or any performance caveat on scanning all pages.

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?

A single efficient sentence with the verb front-loaded and no redundancy. It is well-sized, though it errs toward under-specification rather than true conciseness.

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?

For a 6-parameter search tool with an output-less schema and no annotations, the description is only barely adequate. It conveys the searchable targets but says nothing about result shape, scope (per-site given the required site param), or how results should be consumed.

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%, so every parameter is already documented in the schema. The description names the searchable dimensions (widgets/settings/text) but adds no syntax, matching semantics (substring vs exact), or interaction rules between setting and contains.

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 (Search) and resource (Elementor pages) plus the searchable dimensions (widgets, settings, text content). This distinguishes it from the retrieval siblings like mcp_get_elementor_build or mcp_get_elementor_element, but it never explicitly names or contrasts those alternatives.

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?

There is no when-to-use guidance, no exclusions, and no mention of the sibling retrieval tools it competes with. The agent must infer from the name alone that this is the discovery/filtering tool while mcp_get_elementor_flat and friends are for direct reads.

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

Deploy Server