Skip to main content
Glama
WordPress MCP Server

WordPress MCP Server

by ernestoh0183

revisar_comentarios

List and filter WordPress blog comments by moderation status to review pending, approved, spam, or trash items.

Instructions

Lista los comentarios del blog según su estado de moderación.

Args: estado: Filtro por estado: 'all' (todos), 'hold' (pendientes de revisión), 'approve' (aprobados), 'spam' o 'trash' (papelera). limite: Número máximo de comentarios a devolver (por defecto 10, máx 30).

Returns: Listado con ID del comentario, ID del post, autor, fecha, estado y contenido.

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": "revisar_comentarios"
  }
}

Input Schema

NameRequiredDescriptionDefault
estadoNoall
limiteNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the return fields (ID, post ID, author, date, status, content) and a hard cap of 30 results, which is useful behavioral context, but it omits whether the call requires authentication, how pagination beyond 'limite' works, and whether ordering is stable.

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 front-loaded with a one-line purpose, then uses clean Args/Returns blocks that are easy to scan. The Args/Returns scaffolding is slightly heavy for two parameters, but no sentence is wasted.

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 two-parameter filtered-list tool with an output schema present, the definition covers purpose, both parameters, and result shape. The Returns section is partly redundant against the output schema, but nothing essential for invoking the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it largely does: every allowed value of 'estado' is spelled out with its meaning in Spanish, and 'limite' gets both its default (10) and its ceiling (30). Only minor gaps remain, such as behavior for an invalid estado string.

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 opens with a specific verb+resource: 'Lista los comentarios del blog según su estado de moderación', which clearly separates it from the mutating sibling 'moderar_comentario'. It never names a sibling explicitly, so the differentiation is implied rather than stated.

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?

Usage is implied by the phrase 'según su estado de moderación' and the enumerated estado values, which tell the agent this is a read/filter operation. There is no explicit when-to-use, when-not-to-use, or pointer to a preferred alternative for moderation actions.

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