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

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_list_cpt_items

List WordPress custom post type entries by slug, using optional filters for status, search, page, and per-page limits to retrieve targeted content.

Instructions

List items of a custom post type with optional filters

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": {
      "post_type": "<post_type>"
    },
    "name": "wp_list_cpt_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
searchNo
statusNo
per_pageNo
post_typeYesPost type slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are present, so the description must carry the full behavioral disclosure burden. 'List' implies a read-only operation, but the description does not mention pagination behavior, default status scope, or whether results are limited. It adds no information beyond the verb itself about side effects or safety.

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

Conciseness5/5

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

The description is a single concise sentence with no fluff. It is front-loaded with the core action and resource, and every word contributes to understanding the tool's purpose.

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?

As a listing tool with no output schema and minimal documentation, the description is too sparse. It does not clarify the position among the CPT item family (get/create/update/delete/list), nor explain the return format or pagination behavior. An agent would need to inspect the schema or guess to understand what 'items' entails and how filters affect results.

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 only 20% (only post_type has a description). The phrase 'optional filters' is vague and does not enumerate or explain page, search, status, or per_page, nor how they interact. The description fails to compensate for the low schema coverage.

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 'List items of a custom post type' clearly identifies the action (list), the resource (items of a custom post type), and distinguishes this from siblings like wp_get_cpt_item (single item), wp_list_posts (standard posts), and wp_list_pages (pages). The use of 'custom post type' provides specificity beyond a generic list tool.

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

Usage Guidelines3/5

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

The description implies usage when a user wants to enumerate custom post type items, but it provides no explicit guidance about when to prefer this over wp_list_posts or wp_get_cpt_item. There are no stated alternatives or exclusions, leaving the selection inference entirely to the name and description.

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