Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: List posts

wordpress_list_posts
Read-only

List WordPress posts with pagination, search, and status filters to review titles, excerpts, metadata, and optional content.

Instructions

[UNIFIED] List WordPress posts. Returns paginated list of posts with title, excerpt, status, and metadata.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
siteYes
searchNo
statusNoany
per_pageNo
search_termsNo
include_contentNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv3.4.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds value by disclosing the return shape (title, excerpt, status, metadata) and pagination, but says nothing about authentication, site parameter semantics, or whether include_content inflates results.

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?

Two short sentences that are front-loaded with the action and then the return values; nothing is redundant. The "[UNIFIED]" tag is dead weight that consumes attention without informing the agent.

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

Completeness2/5

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

For a tool with seven parameters, zero schema descriptions, and no output schema, the description is far too thin — an agent cannot tell what status values are valid, what search_terms does versus search, or what include_content changes. Only the return field list partially fills the gap.

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?

With 0% schema description coverage, the description only hints at pagination via "paginated list"; the seven parameters (page, per_page, search, search_terms, status, include_content, site) are otherwise unexplained. The word "metadata" gestures at fields but does not map to any parameter, so the compensation for the coverage gap is minimal.

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?

States a specific verb and resource ("List WordPress posts") and lists the returned fields, so the core action is unambiguous. It does not distinguish itself from siblings such as wordpress_list_pages or wordpress_list_custom_posts, and the unexplained "[UNIFIED]" prefix adds no meaning.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this tool over the many sibling list tools (pages, custom posts, media, categories). Usage is only implied by the name, and no prerequisites or exclusions are given.

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