Skip to main content
Glama

wp_list_pages

List WordPress pages with pagination, search, and status filters to inspect site content or support AI-driven page management workflows.

Instructions

List WordPress pages.

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

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

C2.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it discloses nothing. Only the verb "List" implies a read-only, non-destructive operation; nothing is said about authentication requirements, default result ordering, whether drafts/private pages are included by default, or pagination behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of waste, but its brevity is under-specification rather than economy. There is nothing extraneous to cut, yet far too little is present for a four-parameter listing tool.

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 four parameters, a status enum, pagination limits, and no annotations or output schema, the definition is far too thin. An agent cannot tell what a result item looks like, how results are ordered, or what the default status=any means in practice.

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?

With half the parameters (notably `search` and `status`) undocumented in the schema, the description needs to compensate but does not mention any parameter at all. The `status` enum values are somewhat self-describing, which keeps this above a 1, but the agent gets no guidance on how search matching or status filtering behave.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"List WordPress pages" is essentially the tool name (wp_list_pages) restated in prose. It names the resource but adds no scope detail — no mention of filtering, hierarchy, status, or pagination — that would let an agent distinguish this from wp_list_posts beyond the literal word "pages".

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?

There is no when-to-use guidance, no exclusions, and no reference to alternatives such as wp_list_posts, which the sibling set shows is the nearest comparable tool. The agent must infer that this returns pages rather than posts entirely from the name.

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