Skip to main content
Glama
RaheesAhmed

WordPress MCP Server

by RaheesAhmed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wordpress_get_pages

wordpress_get_pages

Retrieve WordPress pages with hierarchy and custom ordering. Specify pagination using perPage and page parameters.

Instructions

Get pages with hierarchy and ordering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
perPageYes
pageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It mentions hierarchy and ordering, but it does not explain pagination, read-only safety, or any other side effects. The description is too vague to give a clear behavioral picture.

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?

The description is a single, efficient sentence with no unnecessary words. It is appropriately sized for its content, though it omits valuable details.

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 no output schema and no annotations, the description doesn't specify what the return data looks like, what 'hierarchy' and 'ordering' mean, or how pagination is handled. This is incomplete for an agent to use the tool correctly without additional information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has two parameters (page, perPage) with 0% description coverage. The description does not mention or explain these parameters at all, failing to add any meaning beyond their types.

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?

The description clearly states the action ('Get'), the resource ('pages'), and specific characteristics ('with hierarchy and ordering'). This distinguishes it from sibling tools like wordpress_get_posts and other page-related CRUD tools.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It doesn't mention any exclusions, such as 'for posts use wordpress_get_posts', or provide context for usage scenarios.

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

Deploy Server

Other Tools