Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: List pages

wordpress_list_pages
Read-only

Retrieve a paginated list of WordPress pages with metadata, filtered by status, to review site content from an AI assistant.

Instructions

[UNIFIED] List WordPress pages. Returns paginated list of pages with metadata.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>"
    },
    "name": "wordpress_list_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
siteYes
statusNoany
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv3.4.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds that results are paginated and include metadata, which is useful beyond the annotation, but says nothing about default ordering, total counts, or what metadata fields appear.

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, front-loaded with the action and resource. The '[UNIFIED]' prefix is minor noise but nothing is wasted.

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 undocumented parameters, no output schema, and no enum for status, the definition is far too thin for an agent to call it correctly — in particular the required 'site' argument and the accepted status values are left entirely to guesswork.

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?

Schema description coverage is 0% across 4 parameters, so the description carries the burden and fails: 'site' (the required parameter) is never explained, 'status' has no documented values despite defaulting to 'any', and page/per_page are only vaguely implied by the word 'paginated'.

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 clear verb and resource ("List WordPress pages") and mentions the return shape (paginated list with metadata). It does not distinguish pages from the many sibling list tools such as wordpress_list_posts or wordpress_list_custom_posts, so an agent gets no help telling similar resources apart.

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 guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The only hint is implied by the resource name 'pages'.

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