Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Report site-wide widget usage

elementor_widget_usage
Read-onlyIdempotent

Count which Elementor widgets are actually used across a site and how many each page contains. Use it to check widget usage before removing an addon plugin or to find the heaviest pages.

Instructions

Count which Elementor widgets are actually used across the site and how much each page contains. Useful before removing an addon plugin, or to find the heaviest pages.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.2/5.0
Behavior3/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 no behavioral context beyond intent — nothing about scan cost, whether drafts/templates are included, or how the open-world crawl behaves on large sites.

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 short sentences, front-loaded with the core action and followed by use cases; no filler. Slightly thin rather than bloated.

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?

With no output schema, the agent gets only an implication that results include per-widget counts and per-page totals; the exact shape is unstated and the postTypes filter is unexplained, which is a meaningful gap for a reporting tool.

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 coverage is only 50% and the undocumented parameter, postTypes, is never explained in the description — an agent cannot tell whether omitting it scopes to pages only or all post types. The description does not compensate for the schema gap.

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 concrete verb and resource: counts Elementor widget usage site-wide and per-page density. It is clearly distinguishable from the CRUD/list siblings, though it doesn't explicitly name an alternative it is not.

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?

Gives two concrete usage scenarios (before removing an addon plugin, finding heavy pages) but no exclusions or explicit pointers to alternative tools such as elementor_find_elements or elementor_get_outline for narrower inspections.

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