Skip to main content
Glama

mcp_update_elementor_kit

Update Elementor global kit settings such as colors, fonts, and typography by merging supplied values. Send full nested lists, since nested values replace the old ones.

Instructions

Update Elementor global kit settings (colors, fonts, typography). Top-level keys are merged; a nested value such as system_colors replaces the old one whole, so send the complete list. Returns the merged settings.

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
settingsYesKit settings to merge (non-empty)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.14.0
    • changedInput schema / properties / settings / description
      Previous value: -"Kit settings to merge"New value: +"Kit settings to merge (non-empty)"
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "settings"
      -]New value: +[
      +  "site",
      +  "settings"
      +]
  3. First observedv2.0.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it discloses the most consequential non-obvious trait: top-level keys merge while nested values such as system_colors are replaced whole, so the complete list must be sent. It also states the return value. It omits permission/auth requirements and whether the change is reversible, which keeps it off a 5.

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 short sentences, front-loaded with purpose, then the destructive merge caveat, then the return value. No filler, and the most error-prone detail is placed before an agent would commit to a call.

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 mutation tool with zero annotations and no output schema, it covers the essentials: scope, merge hazards, and return behavior. The remaining gap is operational context such as required capabilities or failure modes when an invalid kit key is sent.

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 is 3, but the description earns more by explaining the semantics of the opaque 'settings' object: which merge strategy applies at each nesting level and the requirement to send complete nested lists. That is meaning the schema's 'additionalProperties: {}' does not convey.

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: 'Update Elementor global kit settings (colors, fonts, typography).' The 'global kit' scope and enumerated settings areas distinguish it from sibling mutation tools like mcp_update_elementor_element and mcp_update_elementor_page_settings, though no sibling is 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: this is the tool for changing site-wide styles, and the merge warning hints at how to call it. There is no explicit when-to-use/when-not guidance and no pointer to mcp_get_elementor_kit as the read counterpart or to the page/element updaters as alternatives.

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

Deploy Server

Other Tools