Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Check site status

elementor_site_status
Read-onlyIdempotent

Reports WordPress and Elementor versions, Elementor Pro presence, registered widget types, active kit, user capabilities, and bridge/destructive-operation status to verify site readiness before editing.

Instructions

Report what a site is running: WordPress and Elementor versions, whether Elementor Pro is present, how many widget types are registered, the active kit id, the capabilities of the authenticated user, and whether the bridge plugin and destructive operations are enabled. Run this before a first editing session on an unfamiliar site.

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

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context by disclosing that the tool reports whether the bridge plugin and destructive operations are enabled — a pre-flight safety check not derivable from annotations or schema.

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?

Front-loaded with the verb and the enumerated payload, followed by a single short usage sentence; nothing is redundant. The first sentence is long due to the field list, but every listed item corresponds to a distinct reported fact rather than filler.

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

Completeness5/5

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

There is no output schema, so the description carries the burden of describing return values — and it does so field by field. For a single-optional-parameter read tool with full annotation coverage, nothing an agent needs to call it or interpret the result is missing.

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?

There is a single optional 'site' parameter and schema coverage is 100%, with the schema already explaining both the name format and the omit-to-use-default behavior. The description adds no further parameter meaning, so the baseline 3 applies; the 4 baseline for zero params does not since one param exists.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Report") and enumerates exactly what is reported: WordPress/Elementor versions, Pro presence, widget type count, active kit id, user capabilities, bridge plugin and destructive-operation flags. That enumeration distinguishes it from siblings like elementor_list_sites or elementor_list_widgets, which return site lists or widget catalogs rather than environment state.

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?

Explicitly says when to run it: "before a first editing session on an unfamiliar site," which gives the agent a concrete trigger. It does not state when-not to use it or name a sibling alternative, so it stops short of a 5.

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