wpxmcp

Bulk moderate comments

moderate_comments

Approve, hold, spam, trash, unspam, or untrash multiple comments in one call. Reports per-comment outcomes so you can clear a WordPress moderation queue.

Instructions

Approve, hold, spam, trash — or unspam/untrash — several comments in one call; the practical way to clear a moderation queue. Reports per-comment outcomes rather than failing the whole batch on one error.

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": {
      "ids": "<ids>",
      "action": "<action>"
    },
    "name": "moderate_comments"
  }
}

Input Schema

Name	Required	Description
`ids`	Yes	Comment IDs to act on.
`action`	Yes	What to do with each. unspam/untrash restore the comment's previous status.
`site_id`	No	Which configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv2.0.0Sep 15, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / action / description

Previous value: -"What to do with each."New value: +"What to do with each. unspam/untrash restore the comment's previous status."

changedInput schema / properties / action / enum

Previous value: -[
-  "approve",
-  "hold",
-  "spam",
-  "trash"
-]New value: +[
+  "approve",
+  "hold",
+  "spam",
+  "unspam",
+  "trash",
+  "untrash"
+]

addedInput schema / properties / ids / items / maximum
```
Added value: +9007199254740991
```
addedInput schema / properties / ids / items / minimum
```
Added value: +-9007199254740991
```

First observedv1.0.0Aug 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

It discloses valuable behavioral detail beyond the annotations: per-comment outcomes are reported and a single error does not fail the whole batch. Annotations already signal mutation with readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the description adds useful partial-failure context without contradicting them.

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?

The description is two tight sentences: actions are front-loaded, the use case follows, and the key error-handling behavior closes it. Every clause contributes information with no filler.

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

Completeness4/5

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

For a moderately complex batch tool with no output schema, the description covers scope, action semantics, and high-level response behavior. It could be slightly richer about the exact per-comment result shape and how to route edge cases like a single comment, but the schema fills most remaining invocation details.

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 tool description carries little parameter burden. It restates the available actions and batch scope but adds no meaning beyond what the schema already provides for ids, action, or site_id.

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 and resource—moderating comments—and enumerates the exact actions available: approve, hold, spam, trash, unspam, untrash. It clearly distinguishes itself from single-comment tools by emphasizing 'several comments in one call' and positions itself as the queue-clearing operation.

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: use this for bulk moderation and clearing a moderation queue. However, it does not explicitly state when to use single-comment alternatives like update_comment or delete_comment, so it stops short of full exclusion guidance.

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

Deploy Server