Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp theme activate

wordpress_specialist_wp_theme_activate
Destructive

Activate a WordPress theme by slug, verifying the slug exists and the caller has switch_themes permission, then return the active stylesheet and template after the switch.

Instructions

[UNIFIED] Switch the active theme to slug. Companion verifies the slug exists in wp_get_themes() (S-15) and the caller holds switch_themes. Returns the active stylesheet + template after the switch — useful when activating a child theme (stylesheet differs from template). Requires Airano MCP Bridge v2.14.0+.

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>",
      "slug": "<slug>"
    },
    "name": "wordpress_specialist_wp_theme_activate"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=false), the description adds real behavior: slug-existence verification, a capability check, and the return payload (active stylesheet + template). It does not warn about side effects of a theme switch — widget/menu locations, customizer settings, or reversibility — which is the main remaining gap for a destructive mutation.

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?

Front-loaded with the action, then preconditions, then returns — a sensible order with little waste. The internal ticket reference "(S-15)" and the "[UNIFIED]"/'Companion' framing are jargon that adds no meaning for an agent.

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?

With no output schema, the description correctly explains the return value, and it covers auth and version prerequisites for a destructive mutation. The unaddressed `site` parameter is the only substantive omission.

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 0%, so the description carries the burden for two parameters. It explains `slug` reasonably (a theme slug validated against wp_get_themes()) and ties it to child-theme stylesheet/template behavior, but the `site` parameter is never mentioned at all.

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?

States a specific verb and resource: "Switch the active theme to `slug`." The scope is narrow enough that an agent can separate it from wordpress_specialist_wp_theme_list (read) and wordpress_specialist_wp_theme_install_from_zip (install), without opening a schema.

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 clear preconditions for calling it: the slug must exist per wp_get_themes(), the caller must hold switch_themes, and the bridge must be v2.14.0+. It never states when *not* to use it or names a sibling alternative, so it stops short of a 5.

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