Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Get a widget's settings schema

elementor_get_widget_schema
Read-onlyIdempotent

Read a widget's full control schema—settings, types, defaults, allowed options and responsive flags—before editing, so you avoid guessing control names that save with no visible effect.

Instructions

Read the full control schema for a widget or structural element: every setting it accepts, grouped by panel tab and section, with types, defaults, allowed options and which settings are responsive. Read this before setting unfamiliar widget settings — guessing control names is the most common cause of an edit that saves without visible effect.

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": {
      "name": "<name>"
    },
    "name": "elementor_get_widget_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoUse "element" for container, section and column.widget
nameYesWidget type (e.g. "heading") or element type (e.g. "container").
siteNoConfigured site name. Omit to use the default site.
compactNoTrim CSS selector maps and render hints. Turn off only if you need raw control definitions.
sectionNoReturn only this section of the schema, to keep the response small.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and repeatability are covered. The description adds what annotations cannot: the structure of the returned schema, that settings carry types/defaults/options/responsiveness, and the practical failure mode of guessing control names. It does not discuss response size or limits beyond the schema's own hints.

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?

Three sentences, front-loaded with the verb and payload, then the when-to-use rationale. No filler, and the motivating warning is placed at the end where it lands as a caution rather than delaying the definition.

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 has to describe the return value — and it does so precisely (grouped by tab/section, types, defaults, options, responsive flags). For a read-only introspection tool with 5 well-documented params, nothing an agent needs in order to call it correctly is absent.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline would be 3. The description earns a notch above by explaining that the schema is organized by panel tab and section, which gives structural meaning to the section filter and to what compact trims, rather than merely restating field names.

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?

"Read the full control schema for a widget or structural element" names a specific verb and resource and then enumerates the payload (settings grouped by panel tab and section, with types, defaults, allowed options, responsive flags). This clearly separates it from siblings such as elementor_widget_usage (usage examples) and elementor_list_widgets (enumeration), without the agent needing to open either schema.

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 a concrete trigger for use —"before setting unfamiliar widget settings"—and justifies it with the observed failure mode (edits that save without visible effect). It also hints at response sizing via section/compact. What is missing is any explicit when-not or a named alternative for cases where usage examples, not schemas, are needed.

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