Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp plugin activate

wordpress_specialist_wp_plugin_activate
Destructive

Activates an installed WordPress plugin by slug, resolving it to the plugin file and enabling network-wide activation on multisite when requested.

Instructions

[UNIFIED] Activate an installed plugin by slug. Companion resolves the slug to the plugin file via get_plugins() (S-15) and calls activate_plugin(). When network_wide=true on a multisite install the plugin is activated network-wide (requires manage_network_plugins). Requires Airano MCP Bridge v2.15.0+ and activate_plugins.

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_plugin_activate"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
slugYes
network_wideNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.9/5.0
Behavior4/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=false) by disclosing the slug-to-file resolution path, the underlying activate_plugin() call, multisite network-wide semantics, and the exact capability requirements. It stops short of covering failure modes such as fatal errors on activation or whether an already-active plugin is a no-op.

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?

Dense and front-loaded: the core action leads, followed by mechanism, multisite behavior, and prerequisites in descending importance. The internal marker '(S-15)' is noise, but otherwise every sentence carries information.

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 3-parameter mutation with annotations but no output schema, the description covers mechanism, permissions, and multisite branching adequately. The gaps are the undefined 'site' parameter and no statement of what happens on failure or on an already-active plugin.

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 must carry the parameters. It explains 'slug' (resolved to a plugin file via get_plugins()) and 'network_wide' (multisite-wide activation requiring manage_network_plugins), but leaves 'site' entirely undefined, leaving one of three parameters undocumented.

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 ('Activate an installed plugin by slug') and narrows the scope to already-installed plugins, which implicitly distinguishes it from the install_from_slug/install_from_zip siblings. The mechanism (get_plugins() resolution, activate_plugin()) makes the operation unambiguous.

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?

Provides prerequisite conditions (requires Airano MCP Bridge v2.15.0+ and the activate_plugins capability; manage_network_plugins for network-wide), which is useful gating context. However, it never states when to prefer this over siblings like wp_plugin_install_from_slug or when not to use it, so usage selection is only implied.

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