Skip to main content
Glama
c-sakel
by c-sakel

Kommentare Bulk-Moderation

comment_moderate_bulk

Moderate multiple WordPress comments at once by approving, holding, marking as spam, trashing, or deleting them with a single bulk action.

Instructions

Moderiert mehrere Kommentare auf einmal

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAktion
commentIdsYesArray von Kommentar-IDs
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It only says 'moderates' without mentioning potential destructive effects (e.g., delete or trash), whether permissions are required, or what the response contains. This is a significant gap for a tool that can modify or remove multiple comments.

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?

The description is a single short sentence, front-loaded with the key action and scope. It contains no fillers, but the extreme brevity means it sacrifices helpful context, making it slightly less than excellent.

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?

Despite a simple schema, the tool is a bulk mutation operation with potentially significant side effects. The description omits return values, error handling, and warnings about permanent actions, leaving the agent under-informed. Output schema is absent, so the description should compensate but doesn't.

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?

Both parameters are documented in the schema with descriptions and one has an enum. The description adds no additional meaning about the parameters or their relationship, but since schema coverage is 100%, the baseline of 3 is appropriate.

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?

The description uses the verb 'Moderiert' (moderates) with resource 'Kommentare' (comments) and specifies 'mehrere ... auf einmal' (several at once), clearly indicating a bulk operation. This distinguishes it from single-comment tools like comment_update or comment_delete, though it doesn't enumerate the specific moderation actions.

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?

No explicit guidance on when to choose this tool over single-comment tools or other moderation functions. The description gives no context, prerequisites, or alternative references. The only hint is the 'bulk' aspect, but no direct instruction or exclusion of alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/c-sakel/wp-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server