Skip to main content
Glama

mcp-easy-ai__wp_list_posts

Read-only

Lists WordPress posts. Optional filters: status (publish/draft/pending/private/future/trash — default publish; use "any" to get all statuses), statuses (array of statuses, instead of status), search, categories (array of category IDs), tags (array of tag IDs), author (user ID), author_exclude (array of user IDs to exclude), include / exclude (arrays of post IDs; exclude and sticky false cannot be combined with include, which WordPress lets override them), slug (array of slugs), sticky (boolean), has_password (boolean), post_mime_type, comment_count (exact number of comments), year / monthnum / day, after / before (ISO 8601 date-time range on publish date), date_query, tax_query, meta_key / meta_value / meta_compare, meta_query (WP_Query structures from an allowlist; meta filters only on keys this caller could read: a protected key needs the right to edit every post, a status other than publish needs the right to read other authors' posts in it, and a caller w… Through Royally: its server marks it read-only, so it runs straight away.

Input Schema

NameRequiredDescriptionDefault
dayNoOnly posts published on this day of the month (1-31).
pageNoPage number for pagination.
slugNoOnly posts with one of these slugs.
tagsNoArray of tag IDs to filter by.
yearNoOnly posts published in this year (four digits).
afterNoOnly posts published on or after this ISO 8601 date-time (e.g. "2026-01-01T00:00:00").
orderNoOrder direction.desc
authorNoAuthor user ID to filter by.
beforeNoOnly posts published on or before this ISO 8601 date-time (e.g. "2026-12-31T23:59:59").
offsetNoSkip this many posts (replaces page-based paging when set).
searchNoSearch query to filter posts.
statusNoPost status filter (e.g. publish, draft, pending, private, future).
stickyNotrue: only sticky posts; false: no sticky posts (not with include, which WordPress lets override the exclusion).
contextNoview (default) lists posts you can read; edit lists only posts you can edit and needs edit_posts.view
excludeNoLeave out these post IDs. Not with include: WordPress ignores an exclusion when include is given.
includeNoOnly these post IDs.
orderbyNoField to order results by. include orders by the include list; meta_value and meta_value_num need meta_key.date
site_idNoSite to run this tool on: 8ef2e52b-bd07-4671-a363-ebe8b480b65c (https://demo.royalplugins.com)
meta_keyNoOnly posts that have this meta key (with meta_value: that value). Also the key meta_value / meta_value_num ordering uses.
monthnumNoOnly posts published in this month (1-12).
per_pageNoNumber of posts per page (1-100).
statusesNoSeveral statuses at once (any registered status, or any). Use instead of status, not with it.
tax_queryNoWP_Query tax_query clauses, all of which must match, e.g. [{"taxonomy":"genre","field":"slug","terms":["sci-fi"]}]. Clause keys: taxonomy (one registered for posts), terms, field (term_id, slug, name, term_taxonomy_id), operator (IN, NOT IN, AND, EXISTS, NOT EXISTS), include_children; an object holding clauses and relation (AND/OR) nests. At most 10 clauses, 3 levels.
categoriesNoArray of category IDs to filter by.
date_queryNoWP_Query date_query clauses, all of which must match, e.g. [{"after":"2026-01-01","column":"post_modified"}]. Clause keys: year, month, monthnum, week, w, dayofyear, day, dayofweek, dayofweek_iso, hour, minute, second, after, before, inclusive, compare, column (post_date, post_date_gmt, post_modified, post_modified_gmt); an object holding clauses and relation (AND/OR) nests. At most 10 clauses, 3 levels.
meta_queryNoWP_Query meta_query clauses, all of which must match, e.g. [{"key":"rating","value":"4","compare":">=","type":"NUMERIC"}]. Clause keys: key (required), value, compare, type; an object holding clauses and relation (AND/OR) nests. Keys follow the same readability rule as meta_key. At most 10 clauses, 3 levels.
meta_valueNoMeta value to compare with meta_key's value. Needs meta_key.
raw_columnsNoEdit context only. Each post also carries raw: every database column as WordPress stores it (ID, post_author, post_date, post_date_gmt, post_content, post_title, post_excerpt, post_status, comment_status, ping_status, post_password, post_name, to_ping, pinged, post_modified, post_modified_gmt, post_content_filtered, post_parent, guid, menu_order, post_type, post_mime_type, comment_count, filter). Default false.
has_passwordNotrue: only password-protected posts; false: only posts without a password. A meta filter from a caller who cannot edit every post needs false (or, with edit_posts and edit_published_posts, author set to their own user ID and no author_exclude).
meta_compareNoHow meta_value is compared. Needs meta_key.
comment_countNoOnly posts with exactly this many comments.
author_excludeNoArray of author user IDs to EXCLUDE from results.
post_mime_typeNoOnly posts with this MIME type (WP_Query post_mime_type; posts normally have none).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'its server marks it read-only, so it runs straight away', disclosing the execution behavior (no approval gate). It also surfaces non-obvious access rules: meta filters are limited to keys the caller can read, and non-publish statuses require rights to read other authors' posts.

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

Conciseness2/5

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

One enormous run-on sentence enumerates ~30 filters with no grouping, and it visibly truncates mid-clause ('a caller w… Through Royally'), which reads as damaged output. The lead sentence is well front-loaded, but the bulk repeats schema content that does not need restating.

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

Completeness3/5

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

For a 33-parameter read tool with no output schema, the description covers filter semantics and access constraints well but says nothing about what a returned post looks like, pagination defaults, or total-count behavior. The single missing piece (return shape) matters more here because there is no output schema to fall back on.

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 coverage is 100% and the per-parameter descriptions already document defaults, mutual exclusions, and the meta readability rule, so the description's long parameter inventory is largely duplicative. It consolidates that information usefully but adds little semantic meaning beyond what the schema already 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?

Opens with a specific verb+resource ('Lists WordPress posts'), so there is no ambiguity about what the tool returns. It does not, however, distinguish itself from close siblings such as wp_get_posts, wp_search_posts, or wp_list_pages, leaving that determination to the reader.

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 gives in-tool usage rules (default status is publish, use "any" for all statuses, statuses instead of status, exclude/sticky-false incompatible with include), which is genuinely helpful orientation. But it never says when to pick this tool over an alternative sibling, so the caller gets no routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources