wp_criu

install_plugin_zip

Installs a local ZIP plugin file to a WordPress site and optionally activates it.

Instructions

Instala un plugin ZIP local en un sitio WordPress y opcionalmente lo activa.

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>",
      "zip_path": "<zip_path>"
    },
    "name": "install_plugin_zip"
  }
}

Input Schema

Name	Required	Description
`site`	Yes	site_id, site_label o base_url del sitio.
`zip_path`	Yes	Ruta local al ZIP del plugin.
`activate`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jun 23, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the basic action ('installs and optionally activates') without revealing important details like overwrite behavior, permission requirements, error handling, or return values. This is insufficient for a mutation 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 description is a single, concise sentence (12 words) with no redundancy. It is efficient but could be slightly more structured (e.g., listing key parameters or behaviors). Still, it earns a 4 for being front-loaded and to the point.

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 the tool has 3 parameters and no output schema or annotations, the description is too sparse. It omits what the tool returns (e.g., success indicator, plugin details), error conditions, and prerequisites (e.g., valid ZIP, site accessibility). The agent lacks essential context for correct invocation.

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 67% (site and zip_path have descriptions; activate has a default but no description). The tool description adds no new meaning beyond linking 'local ZIP' to zip_path and 'optionally activates' to activate. It does not clarify formats, restrictions, or relationships. Baseline 3 is appropriate.

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 clearly states the tool installs a local ZIP plugin on a WordPress site and optionally activates it. The verb 'install' and resource 'plugin ZIP local' are specific. This distinguishes it from siblings like list_plugins or plugin_action which handle listing or other actions.

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 description provides no guidance on when to use this tool versus alternatives (e.g., uploading via URL, using admin interface). It does not mention prerequisites, limitations, or when not to use it, leaving the agent without decision support.

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

Deploy Server