Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp elementor detect

wordpress_specialist_wp_elementor_detect
Read-only

Detect whether Elementor is installed on a WordPress site and return its version, Pro status, and edited post types, with a clean false result for non-Elementor sites.

Instructions

[UNIFIED] Report Elementor presence on the site: installed flag, version, Pro flag, and the post types Elementor edits. Returns installed: false cleanly when Elementor is absent — non-Elementor sites do not 404. Requires Airano MCP Bridge v2.13.0+.

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": "wordpress_specialist_wp_elementor_detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, but the description adds genuinely non-obvious behavior: absence of Elementor returns installed:false rather than a 404, and a minimum bridge version (v2.13.0+) is required. That is real context beyond the structured fields, with only output formatting left unstated.

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?

Three short sentences, front-loaded with the purpose and return fields, with the no-404 guarantee placed right after. The bridge version requirement is a slight detour but still earns its place as a deployment constraint.

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 one-parameter read-only detection tool with no output schema, the description covers what is returned and the null case, which is most of what an agent needs. The remaining gap is the meaning/format of the site parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required "site" parameter, so the description must compensate — and it does not. It never explains whether "site" is a slug, ID, URL, or aliased connection name, which is the one thing an agent cannot guess.

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 names a specific verb+resource ("Report Elementor presence on the site") and enumerates exactly what is returned: installed flag, version, Pro flag, and edited post types. It is clearly a detection/read operation, distinguishable from the elementor_get/set/render siblings in spirit, though it never names an alternative explicitly.

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?

When-to-use is only implied — an agent can infer this is the probe to run before elementor_get, elementor_set, or template tools, but the description never says so. No exclusions or prerequisites for choosing between this and wordpress_specialist_wp_elementor_get are given.

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