Today WP

Search the WordPress developer docs

wp_docs

Read-onlyIdempotent

Use when you need the official page for a function, hook, class, block API, REST route, WP-CLI command or common task (nonces, cron, roles, caching...), or a page builder's developer docs: returns the right links with a one-line summary, not the page content. For a step-by-step walkthrough, use wp_howto.

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": {
      "query": "<query>"
    },
    "name": "wp_docs"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes	A function, hook or class name, or a question

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the bar is lower, and the description still adds the single most important behavioral fact: results are links plus a one-line summary, not page body content. That matters because there is no output schema. It stops short of mentioning result limits, ranking, or freshness, which keeps it at 4 rather than 5.

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 sentences, front-loaded with the trigger condition, with the return-shape caveat and the sibling routing both packed in without filler. The long parenthetical enumeration earns its space because each item extends the valid query space.

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?

With no output schema, the description supplies the return shape and the safety profile is already in annotations, so an agent can call this correctly. The only omissions are ordering/ranking and pagination semantics for 'limit', which are minor for a search helper.

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

Parameters4/5

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

Schema coverage is 50%, with only 'query' described in the schema, and the description widens what that parameter accepts beyond the schema's wording by adding block API, REST route, WP-CLI command, common tasks, and page-builder docs. The 'limit' parameter is left to its schema constraints (1-10, default 5), which are self-explanatory, so no real gap remains.

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 combination (find the official developer doc page) and enumerates the resource types covered: functions, hooks, classes, block API, REST routes, WP-CLI commands, common tasks, and page-builder docs. It also states the return shape ('links with a one-line summary, not the page content'), which separates it from a content-fetching tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It opens with an explicit trigger ('Use when you need the official page for...') and names the alternative plus the condition that selects it ('For a step-by-step walkthrough, use wp_howto'). The agent does not have to infer routing between the two lookup tools.

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

All Today WP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?