Skip to main content
Glama
WordPress MCP Server

WordPress MCP Server

by ernestoh0183

gestionar_post

Manage a WordPress post's lifecycle: publish it, revert it to draft, or delete it permanently, and get confirmation with the updated URL.

Instructions

Gestiona el ciclo de vida de una publicación en WordPress (publicar, volver a borrador o eliminar).

Args: post_id: ID del post en WordPress. accion: 'publicar' (status='publish'), 'borrador' (status='draft'), o 'eliminar' (borrado definitivo).

Returns: Confirmación de la acción realizada con la URL actualizada del post.

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": {
      "post_id": "<post_id>",
      "accion": "<accion>"
    },
    "name": "gestionar_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
accionYes
post_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 behavioral burden. It does usefully disclose that 'eliminar' means 'borrado definitivo' (a destructive, presumably irreversible operation) and that the other two actions change post status, and it says the response confirms the action with the updated URL. It omits permission/auth requirements, whether deletion can be undone, and what happens on invalid accion values or missing posts.

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 short and front-loaded, with the core action summary in the first sentence and structured Args/Returns sections after it. Every sentence carries information; the only mild redundancy is the Returns section given an output schema exists.

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?

For a two-parameter mutation tool with no annotations, the definition covers the operations and parameters well, and the output schema means return values needn't be explained further. Still missing is the safety context an agent needs before calling it: permission requirements, confirmation expectations, and error behavior for a definitively destructive delete.

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% and the schema declares 'accion' as a bare string with no enum, so the description is doing real work: it names post_id as the WordPress post ID and defines the three valid accion values with their status mappings ('publicar' → status='publish', 'borrador' → status='draft', 'eliminar' → permanent deletion). It would be a 5 if it stated that other values are rejected or how the mapping is applied.

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 states a specific verb and resource ('Gestiona el ciclo de vida de una publicación en WordPress') and enumerates the three concrete operations (publicar, borrador, eliminar), so an agent knows exactly what the tool does. It does not explicitly distinguish itself from the sibling 'actualizar_post', which is the closest-looking alternative, so it falls short of a 5.

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 enumerated actions: an agent can infer 'use this to publish, revert to draft, or delete'. However, there is no explicit when-to-use vs. when-not guidance, no mention of 'actualizar_post' for content edits, and no prerequisites or preconditions (e.g. post must exist, must be in a given status).

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