Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Get v4 global classes

elementor_get_global_classes
Read-onlyIdempotent

Retrieve the reusable global style classes used by Elementor's atomic element model so you can inspect them across sites. Returns an empty list on sites that predate the feature.

Instructions

Read Elementor v4 global classes — the reusable style classes used by the atomic/Editor One element model. Returns an empty list on sites that predate that feature.

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

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

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world behavior, and the description adds real context beyond them: what the classes are conceptually and the edge-case result (empty list) on sites predating v4. It does not cover auth requirements or rate limits, but those are minor for a read-only lookup.

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 action and resource, then the domain clarification, then the edge-case caveat. Every clause earns its place with no repetition of the name or title.

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 description carries the burden of describing return values; it establishes that a list is returned and that it can be empty, but not what each class entry contains (identifier, label, styles) or ordering. Adequate for selection but incomplete for post-call interpretation.

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% and the single optional site parameter is fully documented in the schema, so the description does not need to explain it. It adds no syntax or selection semantics beyond what the schema provides, which is the baseline case.

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 specific verb and resource ("Read Elementor v4 global classes") and defines the resource in domain terms ("reusable style classes used by the atomic/Editor One element model"), which distinguishes it from the general globals tool. It does not explicitly name a sibling, so an agent must infer the boundary with elementor_get_globals.

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?

Usage is implied by the version scoping (v4/atomic sites) rather than stated as a when-to-use rule, and no alternative such as elementor_get_globals or elementor_set_global_color is named. The note about pre-v4 sites is a helpful precondition but not routing guidance.

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