Skip to main content
Glama
Sign In
wpxmcp

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create a plugin (alias of install)

create_plugin

Install a WordPress plugin from the official repository by slug. Specify status to activate immediately or leave inactive.

Instructions

Install a plugin from the WordPress.org repository. This is the REST API's own naming for the install operation — install_plugin is the clearer name for the same thing.

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

Input Schema

NameRequiredDescriptionDefault
slugYesWordPress.org plugin slug.
statusNoStatus to leave the plugin in after installing: "active" activates it immediately.inactive
site_idNoWhich 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.

  1. Changed3 schema fields changedv2.0.0
    • 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
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status."New value: +"Status to leave the plugin in after installing: \"active\" activates it immediately."
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already mark this as non-read-only and non-destructive, and the description adds the key behavior of downloading/installing from WordPress.org. It does not disclose side effects like filesystem changes, network requirements, or non-idempotence, but it does not contradict annotations either. This is adequate but not rich behavioral context.

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?

Two short sentences, both purposeful: the first states the operation and source, the second preempts naming confusion with install_plugin. No filler or redundant schema repetition.

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?

For a 3-parameter tool with full schema coverage and no output schema, the description plus schema is sufficient to call the tool correctly. It clearly identifies the operation and source, and the schema handles parameter details. It could mention expected return values, but that is not essential for invoking the install.

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 coverage is 100%, so slug, status, and site_id are fully documented in the input schema. The description itself adds no parameter-level detail beyond stating the operation, so the baseline 3 applies.

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 a specific verb ('Install'), a resource ('plugin'), and a source ('WordPress.org repository'), and immediately clarifies that it is the same operation as install_plugin. This makes the tool's function unmistakable and distinguishes it from plugin deletion, activation, or searching.

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 gives clear context: use this tool to install plugins from WordPress.org, and notes that install_plugin is the clearer equivalent name. It does not explicitly state when not to use it or contrast it with alternatives like activate_plugin or delete_plugin, but the alias explanation prevents confusion with the similarly named install_plugin sibling.

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

Deploy Server

Other Tools