wp-cli-mcp

wp_plugin_install

Install WordPress plugins from wordpress.org repository directly via WP-CLI. Specify plugin slug and optionally activate after installation.

Instructions

Install a plugin from wordpress.org

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": {
      "slug": "<slug>"
    },
    "name": "wp_plugin_install"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Plugin slug (e.g. 'woocommerce', 'advanced-custom-fields')
`activate`	No	Activate after install

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 14, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action. It doesn't disclose behavioral traits such as whether installation requires admin permissions, what happens on failure, if it overwrites existing plugins, or any rate limits. This is inadequate for a mutation tool with zero annotation coverage.

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 a single, efficient sentence with zero waste. It's appropriately sized and front-loaded, clearly stating the core purpose without unnecessary elaboration.

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

Completeness2/5

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

Given this is a mutation tool (installing plugins) with no annotations and no output schema, the description is incomplete. It should address permissions, error handling, or what the tool returns, but it only states the basic action, leaving significant gaps for agent understanding.

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 100%, so the schema already documents both parameters (slug and activate). The description doesn't add any meaning beyond what the schema provides, such as examples of slugs or implications of activation. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Install') and resource ('a plugin from wordpress.org'), providing specific purpose. However, it doesn't explicitly differentiate from sibling tools like wp_theme_install (for themes) or wp_plugin_activate (for already installed plugins), which would require a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like wp_plugin_activate (for already installed plugins) or wp_plugin_search (to find plugins first). The description implies usage for installing new plugins but lacks explicit context or exclusions.

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