Handsome Hosting

Manage a WordPress plugin

wp_plugin

Destructive

Install (from the WordPress.org directory; activate true switches it on too), activate, deactivate or update one plugin of a live WordPress site by its slug (the folder name: lowercase letters, digits and hyphens). Runs on the call. Deleting a plugin is not offered here: the person does it in wp-admin. The platform helper hh-migrate is not touched. Refusals: invalid-argument, not-a-target, not-live, migration-open, deploy-open, busy, failed (with WP-CLI's line).

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": {
      "serviceId": "<serviceId>",
      "slug": "<slug>",
      "action": "<action>"
    },
    "name": "wp_plugin"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	the plugin or theme folder name, for example contact-form-7
`action`	Yes
`activate`	No	install only: switch the plugin on after installing it
`serviceId`	Yes	the id of a service on this account

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`error`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / serviceId / description

Previous value: -"the service id from list_services"New value: +"the id of a service on this account"

changedInput schema / properties / slug / description

Previous value: -"the plugin or theme slug as wp_status lists it, for example contact-form-7"New value: +"the plugin or theme folder name, for example contact-form-7"

First observedOct 23, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the readOnlyHint=false and destructiveHint=true annotations, the description discloses that the operation runs on the call, that install comes from WordPress.org, the activate-after-install behavior, deletion exclusion, hh-migrate exclusion, and specific refusal codes. This is unusually rich behavioral context for a mutating tool.

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?

The definition is front-loaded with the action list and constraints, and every sentence contributes useful scope or failure information. The first sentence is dense with nested parentheses, slightly reducing readability.

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?

Given the output schema and annotations, the description covers the main behavioral and failure-mode gaps an agent needs. It is nearly complete, though it does not mention permission prerequisites or account-level context for serviceId.

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 75%, and the description adds useful meaning beyond the schema: slug is the plugin folder name restricted to lowercase letters, digits and hyphens, and activate only matters during install. It does not explain serviceId, but the schema already does.

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 names the exact resource (one WordPress plugin on a live site) and the four supported verbs: install, activate, deactivate, update. It also distinguishes scope by stating that deletion is not offered here and that hh-migrate is untouched.

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?

It gives clear usage context: installs come from the WordPress.org directory, activate true only applies to install, and deletion must be done in wp-admin. It does not explicitly route the agent among sibling tools such as wp_theme or wp_core_update, but the plugin-specific scope is clear.

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

All Handsome Hosting tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?