Skip to main content
Glama
obot-platform

WordPress MCP Server

list_posts

Retrieve WordPress posts with basic information, filtered by status, author, category, tag, or publication date.

Instructions

List posts in WordPress site and get basic information of each post.

Date parameters must be valid ISO 8601 date strings (YYYY-MM-DDTHH:MM:SS).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number to list - default: 1
tagsNoComma-separated list of tag IDs - default: None
orderNoSort order - default: descdesc
contextNoThe context of posts to list - default: viewview
per_pageNoNumber of posts per page - default: 10
statusesNoComma-separated list of statuses (publish, future, draft, pending, private, trash, auto-draft, inherit, request-pending, request-confirmed, request-failed, request-completed) - default: publishpublish
author_idsNoComma-separated list of author IDs - default: None
categoriesNoComma-separated list of category IDs - default: None
search_queryNoLimit results to those matching a string - default: None
publish_afterNoISO 8601 date to filter posts published after - default: None
modified_afterNoISO 8601 date to filter posts modified after - default: None
publish_beforeNoISO 8601 date to filter posts published before - default: None
modified_beforeNoISO 8601 date to filter posts modified before - default: None

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations provided, so description carries the burden. It specifies date format requirement (ISO 8601) but does not disclose other traits like pagination behavior, rate limits, or read-only nature. Output schema exists, reducing need for return value details.

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: first states purpose, second adds a critical formatting constraint. No redundant information, every sentence serves a purpose.

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 list tool with 13 parameters and an output schema, the description covers the main action and a key format rule. Missing mention of pagination defaults, but schema provides those. Overall adequate.

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?

Input schema covers all 13 parameters with descriptions (100% coverage). The description adds a date format reminder, but the schema already includes ISO 8601 for relevant parameters. Minimal added value.

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 action ('List posts') and the resource ('in WordPress site'), distinguishing it from siblings like retrieve_post (single post) and create/update/delete.

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?

No explicit guidance on when to use this tool vs. alternatives. The purpose implies listing over retrieval, but no exclusions or alternative tool names are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/obot-platform/wordpress-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server