mcp-wordpress

wp_pages_list

List WordPress pages by status, author, or parent, with sorting and pagination. Use parent=N to get direct children or parent=0 for top-level pages.

Instructions

List pages with filters. Pages support a hierarchy via parent (use parent=N to list direct children of page N, parent=0 for top-level). Default orders by menu_order ascending — the typical navigation order.

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

Input Schema

Name	Required	Default
`page`	No
`order`	No	asc
`author`	No
`parent`	No
`search`	No
`status`	No	publish
`orderby`	No	menu_order
`per_page`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 6, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description must carry the burden of disclosing behavior. It explicitly describes the hierarchy semantics and the default ordering, which is useful. However, it omits details about return format, pagination, or status filtering behavior, leaving the agent partially in the dark about what to expect.

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. It front-loads the core purpose and packs essential hierarchy information into a concise, readable format. Every sentence adds value without redundancy.

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?

For a tool with 8 parameters, no annotations, and no output schema, the description is incomplete. It explains hierarchy and default ordering but fails to cover filtering semantics, pagination, or response shape. The tool's complexity demands more contextual detail to be safely invoked without further exploration.

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 compensate. It only adds meaningful context for the 'parent' parameter and clarifies the default ordering, but leaves seven other parameters (author, search, status, per_page, page, order, orderby) undefined. Given the high parameter count and zero schema descriptions, this is insufficient compensation.

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 opens with 'List pages with filters', a clear and specific verb-resource-scope statement. It clearly distinguishes from sibling tools like wp_pages_get (single page) and wp_posts_list (posts) by focusing on pages and their hierarchical filtering.

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 provides clear context for when to use this tool, especially for hierarchical page listing via the parent parameter. It states the default menu_order behavior, but does not explicitly mention alternatives or exclusions. The context is strong enough to guide selection without being overly verbose.

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

Deploy Server