wp_criu

activate_theme

Activate a WordPress theme on a specific site by providing the site identifier and the theme's stylesheet. This tool changes the active theme for the site.

Instructions

Activa un tema por stylesheet.

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>",
      "stylesheet": "<stylesheet>"
    },
    "name": "activate_theme"
  }
}

Input Schema

Name	Required	Description	Default
`site`	Yes	site_id, site_label o base_url del sitio.
`stylesheet`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 23, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are present, so the description should disclose behavioral traits. It does not mention side effects (e.g., changing site appearance), required permissions, or error conditions. The brief description fails to provide meaningful behavioral context.

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

Conciseness3/5

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

The description is very concise (one sentence), which is efficient, but it lacks any structure or front-loading of critical information. It could be expanded without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given two parameters, no output schema, and no annotations, the description is too minimal. It fails to clarify that the theme must be installed, what the activation implies (e.g., changing active theme), and what the response looks like.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50%, with only 'site' described. The description adds 'by stylesheet' but does not explain what 'stylesheet' represents (e.g., theme directory name). The description does not compensate for the missing schema description of the second parameter.

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 'Activa un tema por stylesheet' clearly states the action (activate) and resource (theme), specifying the method (by stylesheet). It distinguishes from plugin-related siblings, but lacks clarity on what 'stylesheet' precisely means.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, such as checking if the theme is already active or listing themes first. No prerequisites or exclusions are mentioned.

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

Deploy Server