Skip to main content
Glama

get_pages

Read-only

Retrieve WordPress pages: returns all pages by default, or use search, filters, and page options to get one page plus the total count.

Instructions

Retrieve WordPress pages. Without search, filters or page options, it returns all pages; with them, one page and the total

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, from 1 (optional)
afterNoOnly items published after this date or date-time, ISO8601 in the site's time zone, e.g. '2026-11-01' (optional)
orderNoSort order (optional, default 'desc')
authorNoAuthor user ID (optional)
beforeNoOnly items published before this date or date-time (optional)
searchNoKeyword to search for in the title and content (optional)
statusNoWhich pages to list (optional): 'publish' (default), 'future', 'draft', 'pending', 'private', or 'any', separated by commas. Other than 'publish', the credentials must be allowed to edit pages
orderbyNoSort field (optional, default 'date'). 'relevance' needs search
per_pageNoItems per page, 1-100 (optional). With any of search, filters or page options, only one page is read (default 20 per page), and the result shows the total

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior: with any search/filter/page option the call reads only one page and returns a total, which materially changes how an agent should interpret the result.

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?

Two short sentences with the resource first and the conditional behavior second — no filler. The phrasing 'with them, one page and the total' is elliptically compressed and slightly harder to parse than necessary.

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 9-parameter read-only list tool with fully documented params and no output schema, the description covers purpose and the key result-shape caveat. It leaves what a single page actually contains implicit, but nothing critical for correct invocation is missing.

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% and every parameter carries its own documented meaning (including status permission caveats and the relevance/orderby dependency). The description only gestures at 'search, filters or page options' as a group rather than adding semantics for individual parameters, so 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 and resource: 'Retrieve WordPress pages', which names the page post type rather than a generic content resource. It does not, however, distinguish itself from the get_posts/get_post siblings, so an agent must infer that those cover the posts type.

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 implies when the tool broadens versus narrows ('without search, filters or page options... with them'), which is useful conditional context. It never states when to prefer get_pages over get_posts or get_post, and there is no explicit exclusion of unsupported modes.

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