MCP WordPress CrunchTools

Overview Schema Source Related Servers Discussions Admin

Wordpress List Comments

wordpress_list_comments

Read-only

List WordPress comments with filters for post ID, status, search, pagination, and sort order to review or moderate discussions.

Instructions

List WordPress comments with filtering.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Page number (default: 1)
`post`	No	Filter by post ID
`order`	No	Sort direction (asc, desc)	desc
`search`	No	Search comments by content
`status`	No	Filter by status (approved, hold, spam, trash)
`orderby`	No	Sort by field (date, id)	date
`per_page`	No	Results per page, max 100 (default: 10)

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.6.1Oct 17, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / order / description
```
Added value: +"Sort direction (asc, desc)"
```
addedInput schema / properties / orderby / description
```
Added value: +"Sort by field (date, id)"
```
addedInput schema / properties / page / description
```
Added value: +"Page number (default: 1)"
```

addedInput schema / properties / per_page / description

Added value: +"Results per page, max 100 (default: 10)"

changedInput schema / properties / post / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / post / description
```
Added value: +"Filter by post ID"
```
addedInput schema / properties / search / description
```
Added value: +"Search comments by content"
```

addedInput schema / properties / status / description

Added value: +"Filter by status (approved, hold, spam, trash)"

First observedv0.5.0Aug 19, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered structurally. The description adds only the vague phrase 'with filtering' and discloses nothing beyond that, such as pagination limits or default result ordering. Little value beyond the annotation.

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, front-loaded sentence with no wasted words. It is efficient, though bordering on under-specification rather than genuinely informative brevity.

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?

Seven parameters and a read-only annotation are fully covered by schema and annotations, and an output schema exists so return values need not be explained. The description is minimally adequate but leaves filtering behavior and result semantics entirely to structured fields.

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 seven well-documented parameters (page, post, status, search, orderby, etc.). Per the baseline rule, the schema carries the parameter burden and the description's generic 'filtering' adds no syntax or format detail.

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 (List) and resource (WordPress comments) with a scope qualifier (filtering). It is distinguishable from write-oriented siblings like wordpress_create_comment or wordpress_delete_comment, but it does not differentiate itself from wordpress_get_comment or the other list tools.

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?

The description says nothing about when to use this tool versus alternatives such as wordpress_get_comment or wordpress_search_posts-like siblings. No prerequisites, no context, no exclusions are given.

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