Skip to main content
Glama
ArsNovaSingers

ars-nova-wordpress-mcp

Official

List WordPress Posts

wp_list_posts
Read-onlyIdempotent

List blog posts from arsnovasingers.org with filters for status, author, categories, tags, and search, plus pagination and sorting controls.

Instructions

List blog posts on arsnovasingers.org with filtering, pagination, and sorting.

Returns a paginated list of posts (default 20 per page). Posts are returned newest-first by default. Use status='any' to include drafts/pending/private (requires edit_posts capability).

Args:

  • limit (number): Page size, 1-100. Default 20.

  • offset (number): Pagination offset. Default 0.

  • status (enum): publish | future | draft | pending | private | trash | any. Default 'publish'.

  • search (string): Optional keyword to search title + content.

  • author (number): Optional author ID filter.

  • categories (number[]): Optional list of category IDs to filter to.

  • tags (number[]): Optional list of tag IDs to filter to.

  • orderby (enum): date | modified | id | title | slug | author | relevance. Default 'date'.

  • order (enum): asc | desc. Default 'desc'.

  • response_format (enum): markdown | json. Default 'markdown'.

Returns: Paginated envelope with shape: { "total": number, // Total matching posts on the server "count": number, // Posts in this response "offset": number, // Pagination offset "items": [WPContentItem], // Trimmed post shape (id, title, slug, status, link, excerpt, content_preview, author_id, etc.) "has_more": boolean, "next_offset": number // Present if has_more }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoFilter to posts in any of these tag IDs.
limitNoMaximum results to return (1-100). Default 20.
orderNoSort direction.desc
authorNoFilter to posts by this author ID.
offsetNoNumber of results to skip for pagination. Default 0.
searchNoSearch term to match against title and content.
statusNoFilter by status. 'any' returns all statuses (requires edit_posts capability).publish
orderbyNoField to sort by.date
categoriesNoFilter to posts in any of these category IDs.
response_formatNoOutput format: 'markdown' for human-readable, 'json' for machine-readable.markdown
Behavior5/5

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

Beyond the readOnlyHint annotation, the description adds important behavioral details: pagination envelope fields (has_more, next_offset), default ordering, status filter capabilities, and the trimmed post shape. It does not contradict annotations and enriches the agent's understanding.

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?

The description is well-structured with a purpose sentence, parameter list, and return format. It is reasonably comprehensive for a 10-parameter tool, but it duplicates schema details, which adds length without significant new value.

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

Completeness5/5

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

Given the tool's complexity (10 parameters, no output schema), the description provides a complete return envelope shape, default behaviors, and capability notes. This is sufficient for an agent to invoke the tool correctly without ambiguity.

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 schema already documents every parameter with descriptions. The description's Args section largely restates this information, adding little new meaning. The only extra note about edit_posts capability is already present in the schema's status description, so no meaningful semantic gain.

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 opens with a specific verb and resource: 'List blog posts on arsnovasingers.org' with filtering, pagination, and sorting. This clearly distinguishes it from siblings like wp_list_pages (pages) and wp_get_post (single post).

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 gives clear context by specifying default behavior (20 per page, newest-first) and a capability requirement for status='any'. However, it does not explicitly name alternative tools or state when NOT to use this tool, so it lacks explicit exclusions.

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/ArsNovaSingers/ars-nova-wordpress-mcp'

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