Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp plugin delete

wordpress_specialist_wp_plugin_delete
Destructive

Delete an installed WordPress plugin by slug, with safeguards against removing the active plugin or the bridge itself. Use when a plugin must be fully removed along with its database tables and options.

Instructions

[UNIFIED] Delete an installed plugin by slug. Refuses to delete the Airano MCP Bridge companion itself (S-20) and any currently-active plugin (caller must deactivate first). Lands on the admin tier because plugin delete drops the plugin's database tables / options on uninstall — no undo. Requires Airano MCP Bridge v2.15.0+ and delete_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_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
slugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description goes well beyond that: it explains that uninstall drops the plugin's database tables/options, that there is no undo, which plugins are refused, and the required bridge version and delete_plugins capability. This is exactly the behavioral context an agent needs before an irreversible write.

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: purpose first, then refusals, then the reason for the tier, then prerequisites. Minor waste in the '[UNIFIED]' prefix and the internal '(S-20)' ticket reference, which carry no meaning for an agent.

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

Completeness5/5

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

For a two-parameter destructive tool with no output schema, the description covers the safety profile, the refusal rules, the deactivation prerequisite, and the version/capability requirements. The remaining omission is only the site parameter's expected format.

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. It clarifies that 'slug' means the plugin slug rather than a display name, but says nothing about the 'site' parameter (target site identifier/format). Half the parameters remain semantically unaddressed.

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 ('Delete an installed plugin by slug') plus the exact targeting key, which distinguishes it from install_from_slug, update, activate and deactivate siblings. The scope is immediately clear without opening the 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 explicit preconditions: it refuses to delete an active plugin and directs the caller to deactivate first, and it excludes the Airano MCP Bridge companion itself. The only gap is that it does not name the deactivate sibling tool explicitly, leaving the agent to infer it.

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