wordpress-mcp

mcp_install_plugin

Install a WordPress.org plugin on a specified site using its slug, with an option to activate it immediately after installation.

Instructions

Install a plugin from WordPress.org by slug

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": "mcp_install_plugin"
  }
}

Input Schema

Name	Required	Description
`site`	Yes	Site id (see list_sites)
`slug`	Yes	Plugin slug from WordPress.org
`activate`	No	Activate after install

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv3.4.0Oct 1, 2026

addedInput schema / properties / site

Added value: +{
+  "description": "Site id (see list_sites)",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "slug"
-]New value: +[
+  "site",
+  "slug"
+]

First observedv2.0.0Jun 21, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not say whether install requires elevated permissions, what happens if the plugin already exists, whether files are fetched from the network, or what the response looks like. For a mutation tool this is a significant gap.

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?

A single, front-loaded sentence with no filler. It is efficient, though the terseness contributes to the missing behavioral guidance rather than being paired with it.

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?

For a network-fetch mutation tool with no annotations and no output schema, the description is too thin: no permissions, idempotency, failure modes, or activation consequences are covered. The schema handles parameters, but the behavioral context is largely absent.

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%, with 'site', 'slug', and 'activate' fully documented in the schema, so the baseline is 3. The description adds nothing beyond the schema (e.g., no slug format or activation side-effect detail).

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?

States a specific verb (Install), resource (plugin), and source constraint (from WordPress.org by slug), which implicitly distinguishes it from mcp_install_plugin_zip. No sibling is named explicitly, so it stops short of 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?

The 'from WordPress.org by slug' phrase hints at the source, but there is no explicit when-to-use, when-not, or named alternative (e.g., mcp_install_plugin_zip for a local upload, mcp_search_plugins to find a slug). The agent must infer the routing.

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

Deploy Server