Skip to main content
Glama
alokemajumder

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Activate a theme

activate_theme
Destructive

Switch the live site's active theme to change its entire front-end appearance immediately. Requires confirmation before applying.

Instructions

Switch the site's active theme. This changes the entire front-end appearance immediately, and widget/menu assignments do not always carry across. Requires confirm: true. If you are iterating on a theme you are building, use the draft workflow and publish_draft_theme instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoRequired — this changes the live site's appearance for every visitor.
site_idNoWhich configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.
stylesheetYesTheme directory name to activate.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations flag readOnlyHint=false and destructiveHint=true, but the description adds that the change is immediate, affects all visitors, and that widget/menu assignments may not carry over. It also explains the confirm requirement, which is beyond the annotation. Minor gap: doesn't state reversibility or how to revert, but the destructive nature is well disclosed.

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 sentences, each informative: the core action/effect, the caveat about widget/menu assignments, and the alternative workflow. No fluff, everything earns its place.

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?

Given the tool's complexity (a destructive action with a confirm flag) and with no output schema, the description adequately covers the key behavioral caveats, the confirm requirement, and the alternative. A small gap: no mention of failure modes or how to revert, but the description is sufficient for an agent to select and call correctly.

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 already has 100% coverage for all parameters: stylesheet is described as 'theme directory name', confirm as 'Required — this changes the live site's appearance', and site_id explains optionality and default behavior. The description mentions confirm explicitly but doesn't add extra meaning beyond the schema; baseline 3 is appropriate.

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?

The description states a clear action ('Switch the site's active theme') and its immediate effect ('changes the entire front-end appearance immediately'), which distinguishes it from theme management siblings like install_theme or list_themes. It also contrasts with the draft workflow.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly tells the agent when to use it (activating an existing theme) and when not to (when iterating on a theme being built), explicitly suggesting publish_draft_theme instead. This is strong routing guidance.

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