wpxmcp

Delete a plugin

delete_plugin

Destructive

Remove an installed WordPress plugin permanently after deactivating it. Confirmation required; files and database tables are deleted.

Instructions

Delete an installed plugin from the server. The plugin must be inactive first. Files are removed permanently; many plugins also drop their database tables on uninstall. Requires confirm: true.

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": {
      "plugin": "<plugin>"
    },
    "name": "delete_plugin"
  }
}

Input Schema

Name	Required	Description
`plugin`	Yes	Plugin identifier, e.g. "hello-dolly/hello".
`confirm`	No	Required — plugin files are permanently removed.
`site_id`	No	Which configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.0.0Sep 15, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

First observedv1.0.0Aug 24, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The annotations already mark this as destructive, but the description adds valuable specifics: files are removed permanently, many plugins also drop database tables, and confirm: true is required. This goes well beyond the annotation surface and gives the agent a realistic understanding of consequences.

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?

The description is compact and front-loaded: it states the action first, then the prerequisite, then the irreversible consequences, then the required flag. Every sentence earns its place with no redundancy or filler.

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 destructive delete operation with no output schema, the description is fully adequate. It covers what gets deleted, prerequisites, irreversible effects, and the required confirmation flag. The annotations supply idempotency and destructive hints, and the schema covers parameter details, so nothing essential is missing.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds meaningful emphasis on the confirm parameter ('Requires confirm: true'), which is critical for invoking this destructive operation correctly. It also clarifies the plugin must be inactive, reinforcing the prerequisite tied to the plugin parameter.

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?

The description uses a specific verb and resource ('Delete an installed plugin') and clearly differentiates this from sibling tools like activate_plugin, deactivate_plugin, and install_plugin. The scope is unambiguous and immediately tells the agent what operation this tool performs.

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?

The description clearly states the key prerequisite: 'The plugin must be inactive first.' This gives strong contextual guidance for when this tool is appropriate and implies that deactivation should happen before deletion. However, it does not explicitly name alternative tools like deactivate_plugin for cases where deletion is not intended.

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

Deploy Server