Skip to main content
Glama

wp_list_posts

List WordPress posts by status or search text, with pagination, to find and review site content.

Instructions

List WordPress posts. Optionally filter by status or search text.

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_list_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
searchNo
statusNoany
per_pageNoResults per page (max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. "List" implies a read-only operation, but the description does not disclose pagination behavior, default page size, maximum results, status defaults, or any permission/auth requirements.

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 definition is two short sentences with no wasted wording. The primary purpose is front-loaded, followed immediately by the optional filtering behavior.

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?

With four parameters, no annotations, and no output schema, the definition is too thin. It omits pagination and limit behavior, default status handling, and any indication of what the list response contains, leaving significant context to the schema or inference.

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?

The description adds meaning for two of four parameters by noting filtering by status and search text. The schema documents page and per_page, but status lacks a description beyond its enum and search lacks a schema description; the tool description does not explain status values or search scope in detail.

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?

The description states a specific verb and resource: "List WordPress posts." It is clearly a collection/list operation, which distinguishes it implicitly from single-post siblings like wp_get_post and mutation siblings like wp_create_post. However, it does not explicitly name or contrast with any sibling tool.

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?

The description mentions optional filtering by status or search text, implying usage for browsing or finding posts. It gives no explicit guidance on when to use this tool versus wp_get_post, wp_list_pages, or other listing tools, and offers no exclusions.

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