Skip to main content
Glama
WordPress MCP Server

WordPress MCP Server

by ernestoh0183

gestionar_etiqueta

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

Instructions

Gestiona etiquetas (tags) 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 etiqueta (para crear/actualizar). slug: Slug amigable para la URL (opcional). descripcion: Descripción de la tecnología o concepto para SEO (opcional). etiqueta_id: ID de la etiqueta (requerido para actualizar o eliminar). idioma: 'es' o 'en' (opcional, para vincular en Polylang). etiqueta_traduccion_id: ID de la etiqueta hermana en el otro idioma (opcional).

Returns: Listado de etiquetas 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_etiqueta"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNo
accionYes
idiomaNo
nombreNo
descripcionNo
etiqueta_idNo
etiqueta_traduccion_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations at all, the description carries the full burden, and it omits every behavioral trait that matters: whether 'eliminar' is permanent or reversible, what permissions are required, how duplicate names are handled on 'crear', and whether linking via etiqueta_traduccion_id overwrites an existing translation link. Only the return shape is mentioned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded one-sentence purpose followed by a compact argument list. Every line maps to a parameter or the return value; there is no filler prose.

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?

Seven parameters with one required, no annotations, but an output schema exists so return values need not be elaborated. The description covers arguments and conditional requirements well; the gap is destructive-operation semantics and mode-specific failure modes, which is meaningful but not fatal given the parameter documentation.

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 coverage is 0% and there are no enums in the schema, so the description must compensate — and it largely does, documenting all seven arguments with meaning and marking etiqueta_id as required for update/delete and the Polylang fields as optional. It does not state accepted values for 'idioma' beyond 'es'/'en' being examples, nor validation constraints on slug.

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 set and resource: list, create, update or delete WordPress tags, including SEO descriptions and Polylang linking. An agent knows immediately the domain is tags rather than posts or categories. It does not name a sibling, but the resource noun does most of the disambiguation work.

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?

The accion argument effectively enumerates the modes and the per-argument notes ('requerido para actualizar o eliminar') imply which parameters each mode needs. However, there is no guidance on when to use the 'idioma'/'etiqueta_traduccion_id' path here versus the dedicated vincular_terminos_polylang / vincular_traducciones_polylang siblings, which is a real ambiguity for the agent.

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