Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp plugin deactivate

wordpress_specialist_wp_plugin_deactivate
Destructive

Deactivate an installed WordPress plugin by slug on a chosen site, with optional network-wide scope. It blocks deactivating the Airano MCP Bridge to keep the MCP connection intact.

Instructions

[UNIFIED] Deactivate an installed plugin by slug. Refuses to deactivate the Airano MCP Bridge companion itself — doing so would brick the MCP connection (S-20). 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_deactivate"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
slugYes
network_wideNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds guardrail behavior and auth requirements that annotations cannot express: a hard self-protection refusal that would otherwise brick the MCP connection, plus a minimum bridge version and capability requirement. It does not cover what happens to plugin data or settings after deactivation.

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 dense sentences, front-loaded with the action, then the protective refusal with its rationale, then prerequisites. No filler and nothing repeated from structured fields.

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

Completeness3/5

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

For a destructive mutation with no output schema and 0% schema coverage, the definition covers safety and prerequisites well but leaves the multisite scope parameter undefined and says nothing about the result of the call. Adequate rather than complete.

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 description coverage is 0%, so the description must carry parameter meaning, yet it only addresses the slug parameter ('by slug'). The 'site' target and especially 'network_wide' (a non-obvious multisite concept) are left entirely unexplained in both schema and description.

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?

Names a specific verb and resource ('Deactivate an installed plugin by slug'), which cleanly separates it from wp_plugin_activate and wp_plugin_delete among the siblings. The identifier used (slug) is stated explicitly.

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 a concrete when-not condition (never deactivate the Airano MCP Bridge companion) plus prerequisites (bridge v2.15.0+, activate_plugins capability). It stops short of routing to alternatives such as using wp_plugin_activate to reverse or wp_plugin_delete to remove.

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