Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

List available widgets

elementor_list_widgets
Read-onlyIdempotent

Lists every widget type available on the site with title, categories and Pro status, filterable by name, keyword or category. Check before adding widgets, since installed plugins determine what exists.

Instructions

List every widget type registered on the site, with its title, panel categories and whether it comes from Elementor Pro. Search by name or keyword to find the right one. Always check here before adding a widget — a site only has the widgets its installed plugins provide.

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

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
searchNoFilter by name, title or keyword, e.g. "form" or "slider".
categoryNoFilter by panel category slug, e.g. "basic" or "pro-elements".
includeHiddenNoInclude widgets Elementor hides from the editor panel.

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 declare readOnlyHint, openWorldHint, and idempotentHint. The description adds useful behavioral context beyond those: it lists the attributes returned and explains that available widgets depend on installed plugins, though it does not discuss pagination, rate limits, or authentication.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three front-loaded sentences with no wasted language. It moves from scope to search usage to pre-add guidance, and every sentence contributes to correct selection or invocation.

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 read-only list tool with complete schema coverage and no output schema, this is largely complete: it covers scope, search behavior, returned metadata, and plugin dependency. The only minor gap is that it does not specify whether results are paginated or describe the exact return structure beyond the listed fields.

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 the schema already fully documents all four parameters. The description reinforces the search parameter's purpose, but does not add syntax or meaning for category, includeHidden, or site beyond what the schema provides.

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?

The description states a specific verb and resource: list every registered widget type on the site. It also specifies the returned attributes (title, panel categories, Elementor Pro origin), which distinguishes it from sibling listing tools such as elementor_list_element_types and elementor_list_dynamic_tags.

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 clear usage context: use search to find the right widget and always check this list before adding a widget. The alternative workflow is implied through elementor_add_widget, but there are no explicit when-not-to-use cases or named alternatives beyond the add-widget check.

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