wordpress-mcp-server

List posts or pages

list_posts

Read-only

Retrieve WordPress posts or pages newest first, with keyword search, status filtering, and pagination; credentials are required for non-published statuses.

Instructions

List posts or pages, newest first. Supports keyword search, status filter and paging. Non-published statuses need credentials.

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

Input Schema

Name	Required	Description	Default
`page`	No
`type`	No		posts
`search`	No	Keyword search across title and content
`status`	No		publish
`per_page`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 11, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description still adds real value by disclosing the newest-first ordering and that non-published statuses require credentials. It omits return shape and pagination behavior, which keeps it short of a 5.

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?

Three short sentences, front-loaded with the core action and ordering, with the auth caveat last. Slight redundancy in restating the search/status/paging filters already present in the schema, but nothing is genuinely wasteful.

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 five-parameter, zero-required listing tool with annotations and no output schema, the description covers scope, ordering, filters and the credential caveat. Missing only pagination/return-detail context, which is a modest 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 only 20%, so the description must compensate, and it partially does by mapping to all five parameters: posts/pages (type), keyword search (search), status filter (status) and paging (page/per_page). It gives no enum values, defaults, or the 100-item per_page cap, leaving the schema to carry that weight.

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 posts or pages') plus ordering ('newest first'), which cleanly separates it from get_post and create_draft_post. It does not explicitly name a sibling, but the read-collection scope is unmistakable.

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

Usage Guidelines3/5

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

Usage is only implied: the agent can infer this is the tool for browsing content. The one explicit condition, 'Non-published statuses need credentials,' is an auth prerequisite rather than when-to-use guidance, and no alternative (e.g., get_post for a single item) is named.

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

Deploy Server