Skip to main content
Glama

mcp_list_cpt_posts

Lists posts of any post type with paging totals and filters for status, order, and fields such as ID, title, slug, date, author, and parent.

Instructions

List posts of any post type (id, title, slug, status, date, modified, author, excerpt, parent) with paging totals

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>",
      "type": "<type>"
    },
    "name": "mcp_list_cpt_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1)
siteYesSite id (see list_sites)
typeYesPost type name (e.g. post, page, product, testimonial)
orderNoSort direction (default DESC)
statusNoPost status filter: any (default), publish, draft, pending, private, future, trash, or a comma-separated list
orderbyNoOrder by field (default date)
per_pageNoPosts per page (default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed17 schema fields changedv3.14.0
    • removedInput schema / properties / order / default
      Removed value: -"DESC"
    • changedInput schema / properties / order / description
      Previous value: -"Sort direction"New value: +"Sort direction (default DESC)"
    • removedInput schema / properties / orderby / default
      Removed value: -"date"
    • changedInput schema / properties / orderby / description
      Previous value: -"Order by field"New value: +"Order by field (default date)"
    • addedInput schema / properties / orderby / enum
      Added value: +[
      +  "date",
      +  "modified",
      +  "title",
      +  "name",
      +  "author",
      +  "parent",
      +  "type",
      +  "menu_order",
      +  "comment_count",
      +  "rand",
      +  "none"
      +]
    • removedInput schema / properties / page / default
      Removed value: -1
    • changedInput schema / properties / page / description
      Previous value: -"Page number"New value: +"Page number (default 1)"
    • addedInput schema / properties / page / minimum
      Added value: +1
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
    • removedInput schema / properties / per_page / default
      Removed value: -20
    • changedInput schema / properties / per_page / description
      Previous value: -"Posts per page"New value: +"Posts per page (default 20)"
    • addedInput schema / properties / per_page / minimum
      Added value: +1
    • changedInput schema / properties / per_page / type
      Previous value: -"number"New value: +"integer"
    • removedInput schema / properties / status / default
      Removed value: -"any"
    • changedInput schema / properties / status / description
      Previous value: -"Post status filter"New value: +"Post status filter: any (default), publish, draft, pending, private, future, trash, or a comma-separated list"
    • changedInput schema / properties / type / description
      Previous value: -"Post type name"New value: +"Post type name (e.g. post, page, product, testimonial)"
    • addedInput schema / properties / type / pattern
      Added value: +"^[a-zA-Z0-9_-]+$"
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "type"
      -]New value: +[
      +  "site",
      +  "type"
      +]
  3. First observedv2.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description must carry the behavioral load: it does disclose that results include paging totals and the exact field set, which is useful. It says nothing about permission/auth requirements, whether status filters default to published-only, or how totals behave with filters, leaving meaningful gaps for a 7-param listing tool.

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 the resource named first and the return payload in a compact parenthetical; no filler wording. The field list is slightly dense but each item conveys real return-shape information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only listing tool with fully documented parameters and no output schema, the description supplies the missing return-shape information (field list and paging totals). The main omission is how it relates to the other post-listing siblings, which an agent would need when choosing between them.

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%, with per-parameter descriptions and two enums, so the schema already does the heavy lifting. The description's parenthetical partly mirrors the returned fields rather than adding semantics to parameters like status, orderby, or per_page beyond what the schema states.

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 specific verb ('List') and resource ('posts of any post type'), and enumerates the fields returned plus paging totals, so the agent knows exactly what it gets back. It does not distinguish itself from plausible siblings such as wp_list_posts or wp_search_posts, which keeps it from a 5.

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?

Usage is only implied by the verb and the phrase 'of any post type' — the agent can infer this is the route for querying CPTs, but no when-to-use, when-not-to-use, or alternative tool is named. Nothing is misleading, but nothing actively routes the agent either.

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