Skip to main content
Glama

royal-mcp__wp_update_global_styles

Destructive

Change the site's global styles (Site Editor > Styles) on a block theme. styles and settings are objects in theme.json shape, e.g. {"color":{"background":"#ffffff"},"elements":{"link":{"color":{"text":"#0055aa"}}}}; by default they are merged into what is saved (objects key by key, lists such as a colour palette replaced whole); replace: true saves them as given. Saved through WordPress's own global styles endpoint, so its checks and filtering apply; values WordPress did not keep are listed in not_kept. dry_run shows what would be saved. Requires edit_theme_options. Returns an undo token; undo refuses when the styles were changed again since, unless force. (site: demo.royalplugins.com) Through Royally: waits for a person to approve it in Royally; nothing on the site changes until then.

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": "royal-mcp__wp_update_global_styles"
  }
}

Input Schema

NameRequiredDescriptionDefault
stylesNotheme.json "styles" values to set.
dry_runNo
replaceNoSave styles / settings exactly as given instead of merging (default false).
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)
settingsNotheme.json "settings" values to set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and non-idempotent, and the description earns its keep by explaining exactly what destruction looks like: merge is key-by-key for objects but replaces lists like a colour palette wholesale. It further discloses WordPress-side filtering with a `not_kept` report, an undo token whose reversal is refused if styles changed since unless `force`, and the approval gate that means nothing changes until a person acts.

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?

Purpose is front-loaded in the first clause, then semantics, then constraints. It is dense but nearly every clause carries non-obvious information; the trailing site-identifier parenthetical and the repeated approval sentence add length without adding much for an agent that already has site_id in the schema.

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?

With no output schema, the description still covers returns (undo token, `not_kept` list), permission requirements, failure modes for undo, and the asynchronous approval lifecycle. For a destructive nested-object mutation tool, an agent has everything needed to call it correctly and interpret the result.

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 already 80%, so the schema carries the baseline, and the description adds real meaning on top: `styles`/`settings` are theme.json-shaped with a concrete example payload, and the merge-versus-replace interaction between `replace` and the saved state is spelled out. `dry_run` is only named ('shows what would be saved') without detailing output shape, a minor gap.

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?

The description opens with a specific verb and resource: 'Change the site's global styles (Site Editor > Styles) on a block theme', and names the underlying theme.json shapes being written. That is unambiguous on its own, but it never contrasts itself with near neighbours such as wp_update_custom_css or wp_update_theme_mod, so sibling differentiation is left to inference.

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 clear operating context: merge is the default, `replace: true` switches to whole-object overwrite, `dry_run` previews, and `edit_theme_options` is required. It also warns that the write is gated behind human approval in Royally. What is missing is any explicit statement of when to pick this tool over the other style/CSS update siblings.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources