MCP WordPress CrunchTools

by crunchtools

Overview Schema Source Related Servers Discussions Admin

Python

Local

Wordpress List Posts

wordpress_list_posts

Read-only

List WordPress posts with filters for status, category, tag, or keyword, plus sorting and pagination.

Instructions

List WordPress posts 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_posts"
  }
}

Input Schema

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

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.6.1Oct 17, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / categories / description
```
Added value: +"Filter by category IDs"
```
- 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)"
```
- addedInput schema / properties / page / description
```
Added value: +"Page number (default: 1)"
```
- addedInput schema / properties / per_page / description
```
Added value: +"Results per page, max 100 (default: 10)"
```
- addedInput schema / properties / search / description
```
Added value: +"Search posts by keyword"
```
- addedInput schema / properties / status / description
```
Added value: +"Filter by status (publish, draft, pending, private, future)"
```
- addedInput schema / properties / tags / description
```
Added value: +"Filter by tag IDs"
```
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, so the safety profile is covered. Beyond that, the description discloses nothing behavioral: no note on the 100-item per_page ceiling, default page size, authentication requirements, or what the paginated response contains. It effectively restates the schema's filtering/pagination surface.

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 compact sentence with no filler, and it leads with the verb and resource. It is efficient, though the brevity comes at the cost of the routing and behavioral detail noted elsewhere.

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?

An output schema exists, so return values need not be explained, and annotations cover the read-only nature. However, for a tool in a dense namespace with a near-duplicate search sibling, the absence of any disambiguation or pagination/limit context leaves a meaningful gap.

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 eight parameters (page, per_page, order, orderby, search, status, tags, categories) are already documented in the schema. The description's mention of 'filtering and pagination' adds no syntax, default, or constraint detail beyond that, so the baseline 3 applies.

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 (List) and resource (WordPress posts) plus the capabilities it covers (filtering, pagination). It is clear on its own, but it does not distinguish itself from the close sibling wordpress_search_posts, which an agent could reasonably confuse with keyword-based listing.

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 guidance is given. With siblings like wordpress_search_posts, wordpress_get_post, and wordpress_list_pages in the same namespace, the description should say when listing is preferred over searching or fetching a single post, and it does not.

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