Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_list_comments

List WordPress comments filtered by status or post ID to retrieve specific comment sets for moderation or display.

Instructions

List WordPress comments with optional status and post filters

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wp_list_comments"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
statusNoComment status filter
post_idNoFilter by post ID
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

B3.4/5.0
Behavior2/5

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

Annotations are absent, so the description carries the full burden. It discloses that the tool lists comments but does not state pagination behavior, default comment statuses, result ordering, or authentication/authorization expectations. The read-only nature is only implicit in the word 'List'.

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?

A single sentence with no wasted words. The action, resource, and key filtering capability are all front-loaded efficiently.

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?

The tool has no output schema, no annotations, and only 50% schema description coverage. The description does not clarify return format, pagination defaults, or status filter vocabulary, leaving meaningful gaps for an agent trying to invoke and interpret results correctly.

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?

The description adds filter semantics by saying 'optional status and post filters', which maps to the documented `status` and `post_id` schema properties. However, `page` and `per_page` are undocumented in both the schema and the description, and no allowed status values or defaults are provided.

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 uses a specific verb ('List') and resource ('WordPress comments') and mentions optional filters. This clearly distinguishes it from mutation-focused sibling tools like wp_moderate_comment and wp_reply_to_comment.

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 intended use is implied: retrieving comments with optional filters. However, there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as moderation or reply tools for comment-related mutations.

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