Skip to main content
Glama
WordPress MCP Server

WordPress MCP Server

by ernestoh0183

moderar_comentario

Change a WordPress comment's status—approve, hold, mark as spam, trash—or permanently delete it by comment ID.

Instructions

Modifica el estado de un comentario o lo elimina.

Args: comentario_id: ID del comentario en WordPress. accion: 'aprobar' (approve), 'pendiente' (hold), 'spam', 'papelera' (trash), o 'eliminar_definitivo' (borrado irreversible).

Returns: Confirmación del cambio de estado.

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": {
      "comentario_id": "<comentario_id>",
      "accion": "<accion>"
    },
    "name": "moderar_comentario"
  }
}

Input Schema

NameRequiredDescriptionDefault
accionYes
comentario_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does flag one critical behavior: 'eliminar_definitivo' is irreversible. However it says nothing about permissions/capabilities required, whether 'papelera' is recoverable, or what happens to child replies when a comment is deleted.

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?

Front-loaded purpose sentence followed by compact Args/Returns blocks; no filler. Slightly verbose in restating the English glosses, but that redundancy aids correctness rather than hurting it.

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 mutation tool with an output schema (so return values need no explanation) and no annotations, the description covers the action space and the one irreversible case. Missing are permission requirements and failure behavior, which matter for an unannotated destructive-capable tool.

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 is doing all the work: it identifies comentario_id as a WordPress comment ID and enumerates the accepted values for accion with English glosses (approve, hold, spam, trash). The only gap is that the schema's accion field has no enum constraint, so invalid values are only ruled out in prose.

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+resource: 'Modifica el estado de un comentario o lo elimina', with the exact set of target states enumerated. This clearly separates it from sibling tools like revisar_comentarios (read) or responder_comentario (reply), though it never names an alternative explicitly.

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 when-to-use / when-not-to-use guidance is given. The agent must infer from the action list that this is the moderation path, but nothing says whether to use revisar_comentarios first to obtain the comentario_id, or when deletion should be preferred over trashing.

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