Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Get global design settings

elementor_get_globals
Read-onlyIdempotent

Read a site’s Elementor global design tokens—color and typography palettes, layout defaults, breakpoints, and custom CSS—before styling so existing IDs keep elements consistent.

Instructions

Read the site's Elementor kit: global colour and typography palettes with the ids widgets refer to them by, layout defaults such as container width and breakpoints, and the site custom CSS. Read this before styling anything — using an existing global token keeps a site consistent, and changing one restyles every element bound to 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": "elementor_get_globals"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
includeRawNoInclude the complete raw kit settings object as well as the friendly view.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, so the safety profile is covered. The description adds genuine value by disclosing the consequence of touching a token ("changing one restyles every element bound to it") and by describing the shape of what comes back. It does not, however, explain the includeRaw raw-kit mode or anything about the response beyond the friendly view, so it stops short of full behavioral disclosure.

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, zero padding: the first front-loads the complete enumeration of returned content, the second carries the usage rule and its consequence. Every clause earns its place and the ordering puts the highest-value information first.

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?

With no output schema, the description carries the return-value burden and does so by enumerating palettes with ids, layout defaults, and custom CSS. It is nearly complete for a read-only tool; the only gap is the raw-kit output mode, which the agent must infer from the schema alone.

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 both parameters (site, includeRaw) are documented in the schema, including the default and the meaning of the raw kit object. The description adds no parameter-level detail of its own, so the baseline 3 applies.

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?

States a specific verb and resource ("Read the site's Elementor kit") and then enumerates exactly what is inside: global colour and typography palettes with their ids, layout defaults such as container width and breakpoints, and site custom CSS. An agent can distinguish this from elementor_get_global_classes or elementor_get_page purely from the description.

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?

Gives a clear directive: "Read this before styling anything", with the rationale that reusing an existing global token keeps a site consistent. It does not explicitly name sibling read/write alternatives (e.g. elementor_get_global_classes or elementor_update_globals) or state when this is the wrong call, so guidance is strong on context but lacks explicit exclusions.

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