Skip to main content
Glama
elementor-mcp

elementor-mcp

by heaventree

Update global design settings

elementor_update_globals
Destructive

Merge settings into the Elementor kit to change global colors, typography, container width and breakpoints across the whole site at once. Read globals first and pass only the keys you mean to update.

Instructions

Merge settings into the Elementor kit — colour and typography palettes, container width, breakpoints, theme style defaults. This changes the whole site at once, so read elementor_get_globals first and change only the keys you mean to. A snapshot of the kit is taken before the write.

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

Input Schema

NameRequiredDescriptionDefault
siteNoConfigured site name. Omit to use the default site.
settingsYesKit settings to merge, e.g. {"container_width":{"unit":"px","size":1200}} or a full "system_colors" array. Keys not passed are left alone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so blast radius is known. The description does add real behaviour beyond that: the change is site-wide ('changes the whole site at once'), merging leaves untouched keys alone, and 'a snapshot of the kit is taken before the write' signals recoverability. It omits permissions/auth requirements and what the response contains.

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

Conciseness4/5

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

Three short sentences, front-loaded with the merge verb and affected resources, then the prerequisite read, then the safety note. Every sentence earns its place; no filler or repetition.

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 whole-site destructive mutation with an untyped free-form settings object and no output schema, the description supplies the essential context: scope, merge behaviour, a read-first step and snapshot safety net. Minor gaps remain on the 'site' parameter and on return value, but nothing an agent needs to call it safely is missing.

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 both parameters are already documented, including the merge semantics and an example payload shape. The description echoes the merge rule ('change only the keys you mean to') without adding format or syntax detail, and never mentions the optional 'site' parameter. Baseline 3 applies when the schema does the heavy lifting.

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 ('Merge') and resource ('the Elementor kit'), then enumerates the payload types: colour/typography palettes, container width, breakpoints, theme style defaults. The merge scope distinguishes it from single-key tools like elementor_set_global_color, though that sibling is not named explicitly.

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 concrete pre-call workflow — 'read elementor_get_globals first' — and a scoping rule, 'change only the keys you mean to.' It does not spell out when to prefer elementor_set_global_color or elementor_batch_edit instead, so there is no explicit exclusion guidance.

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