elementor-mcp-agent

list_global_widgets

Read-onlyIdempotent

List all global widgets from Elementor library to manage shared components that update across multiple pages.

Instructions

List all global widgets on a site (Elementor library entries of type 'widget'). These are shared across pages — editing one affects every page using it.

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

Input Schema

Name	Required	Description	Default
`site_id`	No

Output Schema

Name	Required	Description	Default
`total`	Yes
`globals`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0May 27, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint, idempotentHint, openWorldHint. The description adds valuable context: 'editing one affects every page using it', which clarifies the shared nature of global widgets. No contradictions.

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?

Two sentences, front-loaded with the core purpose. No fluff; every word adds meaning or context.

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?

Given the output schema exists (not shown), the description does not need to detail return values. It explains the concept of global widgets and their cross-page effect. However, lacking details on pagination, filtering, or limits for a listing 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 description coverage is 0% and the description does not explain the 'site_id' parameter. It does not add meaning beyond the schema, failing to compensate for the lack of parameter documentation.

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?

Clearly states 'List all global widgets on a site (Elementor library entries of type 'widget')', specifying both the resource (global widgets) and scope (site-level). Differentiates from siblings like list_widgets_in_page by noting they are shared across pages.

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?

The description implies usage for listing global widgets but provides no explicit guidance on when to use this tool versus alternatives (e.g., list_widgets_in_page). No exclusions or prerequisites are mentioned.

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