Skip to main content
Glama

royal-mcp__wp_get_pages

Read-onlyIdempotent

List WordPress pages. Returns id, title, status, URL, date (publish date, site local time), modified (last change, ISO 8601 UTC) and content_length (bytes of stored content — size-check before fetching) for each. Filter by parent to walk the page hierarchy; sort with orderby / order; use modified_after to find pages edited recently. Content edits, Royal MCP custom-field tools, ACF field writes and Elementor writes update modified; other plugins changing only custom fields may leave it unchanged. (site: demo.royalplugins.com) Through Royally: read-only, runs straight away.

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": "royal-mcp__wp_get_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderNoasc or desc. Default when orderby is given: asc (A to Z) for title, desc for every other sort.
parentNoParent page ID — returns only direct children of this page
statusNopublish (default), one status, or any (every status you can read except trash), so a draft you just created can be found.
orderbyNoSort field. Without orderby or modified_after, pages are listed by title A to Z.
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)
per_pageNoNumber of pages (default 10, max 100)
modified_afterNoOnly items last modified after this moment: a date (2026-11-01) or date and time (2026-11-01T09:30:00Z). No timezone means UTC.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / modified_after
      Added value: +{
      +  "description": "Only items last modified after this moment: a date (2026-11-01) or date and time (2026-11-01T09:30:00Z). No timezone means UTC.",
      +  "type": "string"
      +}
    • addedInput schema / properties / order
      Added value: +{
      +  "description": "asc or desc. Default when orderby is given: asc (A to Z) for title, desc for every other sort.",
      +  "enum": [
      +    "asc",
      +    "desc"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / orderby
      Added value: +{
      +  "description": "Sort field. Without orderby or modified_after, pages are listed by title A to Z.",
      +  "enum": [
      +    "date",
      +    "modified",
      +    "title",
      +    "menu_order",
      +    "id"
      +  ],
      +  "type": "string"
      +}
  2. Added
  3. Removed
  4. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds real behavioral context: exact return fields with units and timezone conventions, the advice to check content_length before fetching, and a nuanced caveat that only some write paths bump 'modified'. It also confirms the call executes immediately without approval.

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?

Front-loaded with purpose and return shape, then filtering/sorting hints, then caveats — good information ordering with no filler sentences. The parenthetical site domain duplicates the site_id enum description and the 'read-only, runs straight away' clause largely restates annotations, so it is slightly over-packed rather than wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining the response and does so field-by-field, including the subtle 'modified' semantics that affect modified_after filtering. For a 7-parameter, all-optional listing tool, nothing essential 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 coverage is 100%, so enum values and defaults (per_page 10/max 100, status default publish, order defaults per orderby) are already documented in the schema. The description reinforces parent as a hierarchy walker and modified_after as a recency filter, but adds no syntax or format detail beyond what the schema states.

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

Purpose5/5

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

Opens with a specific verb+resource ('List WordPress pages') and immediately enumerates the returned fields, which cleanly separates it from the singular royal-mcp__wp_get_page and from royal-mcp__wp_get_posts. An agent can pick this tool without opening the schema.

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

Usage Guidelines4/5

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

Gives concrete usage patterns: filter by parent to walk the page hierarchy, sort via orderby/order, and use modified_after to find recently edited pages, plus a size-check hint before fetching content. It stops short of naming explicit alternatives (e.g. wp_get_page for a single page, wp_search for text lookup) or stating when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources