wordpress-mcp

wp_get_namespaces

List all available WordPress REST API namespaces for a site, including custom endpoints added by plugins, to identify routes before making API calls.

Instructions

List available REST API namespaces (plugins may add custom endpoints)

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

Input Schema

Name	Required	Description	Default
`site`	Yes	Site id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv3.4.0Oct 1, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / site
```
Added value: +{
+  "description": "Site id (see list_sites)",
+  "type": "string"
+}
```
- addedInput schema / required
```
Added value: +[
+  "site"
+]
```
First observedv2.0.0Jun 21, 2026

TDQS

A3.6/5.0

Behavior3/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. 'List' strongly implies a read-only operation, and the note that plugins may add custom endpoints usefully signals result variability, but there is no explicit statement about permissions, side effects, or pagination.

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 a single compact sentence with zero filler, and the core purpose is front-loaded. The parenthetical is short and adds relevant scope rather than bloat.

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 simple read-only discovery tool with one fully documented parameter, the description is nearly complete: it states what is returned and notes plugin-added custom endpoints. The lack of annotations and an output schema leaves minor gaps around response format and permissions, but nothing critical is missing.

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% and the single parameter ('site') is documented in the schema as 'Site id (see list_sites).' The description adds no parameter-level meaning beyond what the schema already provides, so the baseline of 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 states a specific verb-resource pair: 'List available REST API namespaces.' It is immediately clear what the tool returns, and no sibling tool shares this discovery purpose, so an agent can identify it without opening the schema.

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 gives no explicit when-to-use guidance, no when-not-to-use conditions, and names no alternatives. The parenthetical about plugins adding custom endpoints adds context but does not tell the agent when this tool is preferable to siblings like mcp_get_system_info or wp_site_info.

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

Deploy Server