Skip to main content
Glama
WordPress MCP Server

WordPress MCP Server

by ernestoh0183

gestionar_categoria

Manage WordPress categories by listing, creating, updating, or deleting them, with SEO descriptions and Polylang translation linking for multilingual sites.

Instructions

Gestiona categorías en WordPress: listar, crear, actualizar o eliminar, con soporte para descripciones SEO y vinculación Polylang.

Args: accion: 'listar', 'crear', 'actualizar', o 'eliminar'. nombre: Nombre de la categoría (para crear/actualizar). slug: Slug amigable para la URL (opcional). descripcion: Descripción temática para SEO y GEO/AEO (opcional). categoria_id: ID de la categoría (requerido para actualizar o eliminar). idioma: 'es' o 'en' (opcional, para vincular en Polylang). categoria_traduccion_id: ID de la categoría hermana en el otro idioma (opcional).

Returns: Listado de categorías o confirmación de la operación realizada.

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

Input Schema

NameRequiredDescriptionDefault
slugNo
accionYes
idiomaNo
nombreNo
descripcionNo
categoria_idNo
categoria_traduccion_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/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 disclosure burden. It does reveal useful preconditions (categoria_id required for update/delete) and a return shape (listing or operation confirmation), but it says nothing about the consequences of 'eliminar' — irreversibility, whether categories with assigned posts can be deleted, or required capability/permissions.

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?

Purpose is front-loaded in one sentence, then a compact Args block, then Returns. Almost every line carries information for a 7-parameter tool. The Returns section is the weakest line since an output schema already exists, but it is short enough not to be wasteful.

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 multi-action CRUD tool with seven parameters and an output schema, the operation and parameter coverage is adequate, but the destructive branch (eliminar) and the Polylang-linking branch are under-described relative to their risk and complexity. An agent has enough to call it, but not enough to call it safely in edge cases.

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 largely does: all seven parameters are explained, optionality is flagged, and the key omission in the schema — the allowed values of 'accion' (listar/crear/actualizar/eliminar), which has no enum — is spelled out. Minor gap: it doesn't clarify the slug/nombre format or how idioma interacts with categoria_traduccion_id beyond one mention.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (WordPress categories) and enumerates the four concrete operations (listar, crear, actualizar, eliminar). An agent can immediately distinguish this from gestionar_etiqueta, gestionar_post, or the Polylang linking siblings by resource alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Each argument is annotated with the action it belongs to — nombre 'para crear/actualizar', categoria_id 'requerido para actualizar o eliminar', idioma 'para vincular en Polylang' — which gives real per-action routing guidance. What's missing is guidance versus alternatives: there are dedicated siblings vincular_terminos_polylang and vincular_traducciones_polylang, and the description never says whether to use this tool or those for language linking.

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