Skip to main content
Glama

wp

Run allowed WP-CLI commands on a WordPress site to list plugins, check available updates, and inspect site details while sensitive files stay hidden.

Instructions

Run an allowed WP-CLI command. args without 'wp', e.g. ["plugin", "list", "--update=available"].

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": {
      "args": "<args>"
    },
    "name": "wp"
  }
}

Input Schema

NameRequiredDescriptionDefault
argsYes
siteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.2

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false. The description adds meaningful context with 'allowed', signalling an external allowlist that limits which commands work — something not in the annotations, so this is useful. But it neither enumerates nor hints at that allowlist, nor does it explain side effects, failure modes for blocked commands, or which site's state is touched.

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?

Two short sentences, front-loaded with the action and immediately followed by the argument format plus a concrete example. Nothing is padded, though a hair more structure would help given there are two distinct parameters.

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?

This is a generic executor with no output schema, 0% schema coverage, and a destructive-looking capability profile. The description should explain the allowlist boundary, the site parameter's semantics, and roughly what output or error to expect; it covers only the args format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must supply parameter meaning. It does well for args — saying to omit the leading 'wp' and showing the tokenized example removes a real ambiguity. The site parameter, however, is never mentioned: its purpose, whether it defaults to the current site, and what a null value means are all left undefined.

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 gives a specific verb+resource combo (run a WP-CLI command) and adds a key constraint: the command must be 'allowed'. The example (["plugin", "list", "--update=available"]) makes the shape concrete. However, it does not distinguish itself from the sibling wp_commands, leaving the agent to guess which of the two is appropriate.

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?

Other than 'allowed', there is no guidance on when to use this tool versus wp_commands, what 'allowed' means, or what happens if a disallowed command is attempted. The example is illustrative of format only, not of usage context.

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