MCP WordPress CrunchTools

Overview Schema Source Related Servers Discussions Admin

Wordpress List Pages

wordpress_list_pages

Read-only

Retrieve WordPress pages with filters for status, parent, search, and ordering, plus pagination to browse large page lists.

Instructions

List WordPress pages with filtering and pagination.

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

Input Schema

Name	Required	Description	Default
`page`	No	Page number (default: 1)
`order`	No	Sort direction (asc, desc)	desc
`parent`	No	Filter by parent page ID
`search`	No	Search pages by keyword
`status`	No	Filter by status (publish, draft, pending, private, future)
`orderby`	No	Sort by field (date, title, id, modified, menu_order)	date
`per_page`	No	Results per page, max 100 (default: 10)

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv0.6.1Oct 17, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / order / description
```
Added value: +"Sort direction (asc, desc)"
```
- addedInput schema / properties / orderby / description
```
Added value: +"Sort by field (date, title, id, modified, menu_order)"
```
- addedInput schema / properties / page / description
```
Added value: +"Page number (default: 1)"
```
- addedInput schema / properties / parent / description
```
Added value: +"Filter by parent page ID"
```
- addedInput schema / properties / per_page / description
```
Added value: +"Results per page, max 100 (default: 10)"
```
- addedInput schema / properties / search / description
```
Added value: +"Search pages by keyword"
```
- addedInput schema / properties / status / description
```
Added value: +"Filter by status (publish, draft, pending, private, future)"
```
First observedv0.5.0Aug 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, and the output schema covers returns, so the bar is lower. The description adds only 'filtering and pagination,' which restates the schema rather than disclosing anything new (e.g., default status scope, whether drafts are included, pagination limits).

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?

A single front-loaded sentence with no wasted words. It is compact, though the brevity edges into under-specification rather than optimal density.

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

Completeness3/5

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

With an output schema, full param coverage, and a readOnly annotation, much of the burden is carried structurally, so the thin description is survivable. What's missing is routing relative to the overlapping list/search siblings, which the structured fields cannot supply.

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%, so all seven parameters are already documented with defaults and value hints in the schema. The description mentions 'filtering' generically but adds no syntax or semantics beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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?

States a specific verb and resource ('List WordPress pages') with the added scope of filtering and pagination, so the agent knows it's a read/listing operation. However, it never distinguishes itself from siblings like wordpress_list_posts or wordpress_search_posts, which could plausibly cover the same filtering role.

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?

No when-to-use, when-not-to-use, or alternative routing is provided. The agent is left to infer whether filtered listing should go here or to wordpress_search_posts, even though that sibling exists and overlaps.

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