Skip to main content
Glama
WordPress MCP Server

WordPress MCP Server

by ernestoh0183

responder_comentario

Reply to a specific WordPress post comment by providing the parent comment ID, post ID, and response text.

Instructions

Publica una respuesta a un comentario específico de un post.

Args: comentario_id: ID del comentario padre al que se responde. post_id: ID del post donde se encuentra el comentario. contenido: Texto de la respuesta.

Returns: Confirmación con el ID del nuevo comentario generado.

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>",
      "post_id": "<post_id>",
      "contenido": "<contenido>"
    },
    "name": "responder_comentario"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYes
contenidoYes
comentario_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It says the tool creates a reply and returns a confirmation with the new comment ID, but says nothing about required permissions, moderation/spam state of the created reply, or whether the action is reversible.

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 one-line purpose followed by structured Args and Returns blocks, with no filler. The Returns note is somewhat redundant given an output schema exists, but it costs little.

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?

Parameter naming and the return confirmation are covered, and the output schema relieves it of explaining response shape. For a write operation with zero annotations, however, the absence of permission, prerequisite, and side-effect information leaves a real gap.

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 does: it explains that comentario_id is the parent comment being replied to, post_id locates that comment, and contenido is the reply text. That parent-vs-child relationship is meaningful semantics the bare schema does not convey.

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 and resource: 'Publica una respuesta a un comentario específico de un post.' It is clearly distinguishable from moderation-type siblings such as moderar_comentario, though it doesn't name any 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?

There is no when-to-use or when-not guidance, no prerequisites (e.g. whether the parent comment must exist or be approved), and no mention of any alternative tool. Usage is only implied by the verb 'Publica una respuesta'.

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