Skip to main content
Glama

wordpress_list_pages

Read-onlyIdempotent

Retrieve WordPress pages from a site using credentials, with optional search filtering and a configurable result limit.

Instructions

List WordPress pages.

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_url": "<site_url>",
      "username": "<username>",
      "app_password": "<app_password>"
    },
    "name": "wordpress_list_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPages to return (max 100, default 10)
searchNoSearch term
site_urlYesWordPress site URL
usernameYesWordPress username
app_passwordYesWordPress application password

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond that — no mention of pagination behavior, default page size, result ordering, or what happens when search matches nothing.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though the economy comes at the cost of the details captured in the other dimensions.

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?

There is no output schema, so the description should describe the return shape (list of page objects, fields available) and pagination semantics; it does neither. For a tool requiring site URL plus credentials, a note about authentication/scope would also be expected.

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%, so all five parameters (including limit, search, and the three auth fields) are already documented in the schema. The description contributes no additional parameter meaning, which is the expected baseline when the schema does the heavy lifting.

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 ('List WordPress pages'), which is enough to distinguish it from siblings like wordpress_list_posts and wordpress_get_post. However, it offers no scope detail (all pages vs. filtered), so differentiation rests entirely on the 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?

The description gives no guidance on when to use this versus wordpress_get_post, wordpress_list_posts, or any other listing tool. It doesn't mention that authentication is required or that results can be narrowed via search/limit, leaving the agent to infer everything from the schema.

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