wpxmcp

List content

list_content

Read-only

List WordPress content by type with filtering, search, ordering, and pagination. Returns compact summaries to avoid flooding; request full content only when needed.

Instructions

List items of any content type — posts, pages, or a custom post type — with filtering, search, ordering and pagination. Returns compact summaries by default so a listing never floods the context; pass full_content: true only when you genuinely need bodies.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Which page of results to return.
`slug`	No	Filter by exact slug.
`tags`	No	Tag IDs to include.
`type`	No	Content type slug (post, page, or a CPT such as "product"). Run discover_content_types if unsure.	post
`after`	No	Only items published after this ISO 8601 date.
`order`	No	Sort direction.	desc
`author`	No	Filter to one author's user ID.
`before`	No	Only items published before this ISO 8601 date.
`fields`	No	Return only these top-level fields, overriding the default summary shape. Also sent as _fields so WordPress returns less.
`parent`	No	Filter to children of this parent ID (0 for top-level items).
`search`	No	Free-text search across title and content.
`status`	No	Filter by status: publish, draft, pending, private, future, trash, or "any". Anything other than publish requires authentication.
`sticky`	No	Posts only: true for only sticky posts, false to leave them out.
`exclude`	No	Leave out these IDs.
`include`	No	Only these IDs.
`orderby`	No	Which field to sort by. "relevance" requires `search`; "include" requires `include`.	date
`site_id`	No	Which configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.
`per_page`	No	How many results per page (WordPress caps this at 100).
`categories`	No	Category IDs to include.
`full_content`	No	Include the full content body of each item. Off by default — listings are for finding things.
`modified_after`	No	Only items modified after this ISO 8601 date.
`taxonomy_filters`	No	Filter by any custom taxonomy, keyed by REST base, e.g. {"product_cat": [12]}.

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv2.0.0Sep 15, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / author / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / author / minimum
```
Added value: +-9007199254740991
```

addedInput schema / properties / exclude

Added value: +{
+  "description": "Leave out these IDs.",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "type": "array"
+}

changedInput schema / properties / fields / description

Previous value: -"Return only these top-level fields, overriding the default summary shape."New value: +"Return only these top-level fields, overriding the default summary shape. Also sent as _fields so WordPress returns less."

addedInput schema / properties / include

Added value: +{
+  "description": "Only these IDs.",
+  "items": {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  "maxItems": 100,
+  "type": "array"
+}

changedInput schema / properties / orderby / description

Previous value: -"Which field to sort by."New value: +"Which field to sort by. \"relevance\" requires `search`; \"include\" requires `include`."

addedInput schema / properties / page / maximum
```
Added value: +9007199254740991
```

changedInput schema / properties / parent / description

Previous value: -"Filter to children of this parent ID."New value: +"Filter to children of this parent ID (0 for top-level items)."

addedInput schema / properties / parent / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / parent / minimum
```
Added value: +-9007199254740991
```

changedInput schema / properties / per_page / description

Previous value: -"How many results per page."New value: +"How many results per page (WordPress caps this at 100)."

addedInput schema / properties / sticky

Added value: +{
+  "description": "Posts only: true for only sticky posts, false to leave them out.",
+  "type": "boolean"
+}

addedInput schema / properties / taxonomy_filters / propertyNames
```
Added value: +{
+  "type": "string"
+}
```

First observedv1.0.0Aug 24, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and destructiveHint, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: it returns compact summaries by default specifically to avoid flooding context, and full_content should only be requested when genuinely needed. This gives the agent useful expectations about output size and side effects.

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?

Two sentences with no filler. The first sentence front-loads the core action and scope; the second provides the most decision-relevant behavioral guidance. Every clause earns its place.

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 complex 22-parameter tool, the description is complete enough for selection and invocation: it establishes scope, filtering options, output shape, and the one parameter that could bloat results. There is no output schema to explain return values, but the compact-summaries note covers the most important expectation.

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 the input schema already documents every parameter thoroughly. The description adds a small amount of extra guidance around full_content and the compact-summary default, but it doesn't need to compensate for missing parameter semantics. Baseline 3 is appropriate.

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 clearly states a specific verb and resource: 'List items of any content type' with filtering, search, ordering, and pagination. It distinguishes itself from single-item retrieval tools like get_content by emphasizing listing and compact summaries, though it doesn't explicitly name sibling alternatives.

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

Usage Guidelines4/5

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

The description provides clear context for when to use the tool: when you need a listing of content items. It also gives guidance on when to pass full_content: true. However, it doesn't explicitly state when NOT to use it or point to single-item alternatives like get_content or search_site.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

List content

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools