Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_list_posts

Retrieve WordPress posts by applying filters for status, search query, page, and per-page count to get the exact list you need.

Instructions

List WordPress posts with optional filters

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

Input Schema

NameRequiredDescriptionDefault
pageNo
searchNo
statusNo
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behaviors. It does not mention pagination defaults, sorting order, or that the response contains an array of post objects. This lack of behavioral detail increases the risk of misuse.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, making it concise and front-loaded. However, it is too brief and omits crucial details; conciseness sacrifices completeness.

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 4 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return format, pagination behavior, or default values. Given sibling tools with similar patterns, more context is needed for correct invocation.

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 coverage is 0%, and the description adds no parameter explanations. While parameter names (status, per_page, page, search) are somewhat self-explanatory, the description fails to clarify their roles or constraints, leaving the AI to infer.

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 verb 'List' and the resource 'WordPress posts', and the optional filters are mentioned. It distinguishes from siblings like wp_list_pages and wp_list_media, which list different content types.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., wp_list_pages). There is no mention of prerequisites, when not to use, or context for filtering. The description is purely definitional.

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