Skip to main content
Glama

wordpress_list_posts

Read-onlyIdempotent

Retrieve WordPress posts from a site, with optional search, status filtering, and result limits, to review or manage content via the UnClick MCP Server.

Instructions

List WordPress posts, optionally by search term.

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_url": "<site_url>",
      "username": "<username>",
      "app_password": "<app_password>"
    },
    "name": "wordpress_list_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPosts to return (max 100, default 10)
searchNoSearch term
statusNoFilter by status (publish, draft, ...)
site_urlYesWordPress site URL
usernameYesWordPress username
app_passwordYesWordPress application password

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds only that the search filter is optional; it says nothing about pagination limits, auth failure behavior, or result ordering beyond what the schema already states.

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?

A single well-formed sentence with the resource front-loaded and the optional filter trailing. No wasted words, though it is arguably under-informative rather than optimally sized.

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?

With 100% schema coverage and complete annotations, the definition is minimally sufficient to invoke the tool. However, for a 6-parameter authenticated tool with no output schema, it omits pagination behavior and result shape, leaving gaps an agent may need.

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%, with limit, search, status, and all three auth parameters documented inline. The description restates the 'search term' parameter but adds no syntax, matching behavior, or default semantics beyond the schema, so baseline 3 applies.

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') that an agent can distinguish from wordpress_get_post and, by implication, wordpress_list_pages. It does not explicitly name or contrast with those siblings, so it falls short of a 5.

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 phrase 'optionally by search term' implies the main usage variant (browse vs. filtered search), but there is no explicit when-to-use, when-not-to-use, or routing to wordpress_get_post for single-post retrieval. Usage is only implied.

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