Skip to main content
Glama
Sign In
wpxmcp

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List allowed WP-CLI commands

list_cli_commands
Read-only

List every WP-CLI command accepted by run_wp_cli, including write status, and filter by substring to see which actions are allowed before execution.

Instructions

List every WP-CLI command run_wp_cli will accept. The allowlist is default-deny: anything not listed here is refused, no matter how it is phrased. Each entry says whether it writes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_cli_commands"
  }
}

Input Schema

NameRequiredDescriptionDefault
filterNoShow only commands containing this substring, e.g. "plugin".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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
  2. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint and destructiveHint, but the description adds meaningful behavioral detail: the allowlist is enforced as 'default-deny' and 'no matter how it is phrased', and each returned entry indicates whether it writes. This goes beyond the structured hints and helps the agent understand enforcement semantics.

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 two sentences with no filler. The main purpose is front-loaded, followed by the critical allowlist behavior and the note that entries indicate write status. Every sentence adds distinct, valuable information.

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

Completeness5/5

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

For a read-only list tool with one optional parameter and no output schema, the description covers everything needed to use it correctly: what it lists, how the allowlist behaves, and what each entry contains. No missing information is likely to cause incorrect 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?

The single optional parameter, filter, is already fully described in the schema with an example ('Show only commands containing this substring, e.g. "plugin"'). With 100% schema coverage, the description needs to add little, and it does not attempt to explain the parameter further. 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 names a specific verb and resource: it 'List[s] every WP-CLI command run_wp_cli will accept.' This clearly identifies what the tool does and ties it to its sibling run_wp_cli. The scope ('accepted', 'allowlist') also differentiates it from generic command-listing tools.

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 makes the usage context explicit: because the allowlist is 'default-deny', anything not listed is refused, so this tool is the source of truth for what run_wp_cli will accept. It does not explicitly spell out 'use this before calling run_wp_cli' or name alternatives, but the default-deny statement strongly implies when it should be consulted.

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