Skip to main content
Glama
WordPress MCP Server

WordPress MCP Server

by ernestoh0183

publicar_borrador_wp

Create or update a WordPress draft post with categories, tags, SEO slug, excerpt, featured image, and Polylang language links for multilingual publishing.

Instructions

Crea un nuevo post o actualiza uno existente en WordPress en estado 'draft' (borrador).

Soporta categorías, etiquetas técnicas, slug SEO, extracto descriptivo, imagen de portada y asignación/vinculación de idioma en Polylang.

Args: titulo: Título del post. contenido_html: Cuerpo completo del post en HTML limpio (h2, p, code, etc.). imagen_portada_id: ID devuelto previamente por 'subir_imagen_portada' (opcional). categorias: Lista de IDs de categorías de WP (ej. [132, 137]). etiquetas: Lista de IDs de etiquetas de WP (ej. [147, 157]). slug: Slug amigable para la URL del post (ej. 'caddy-docker-microservices'). extracto: Resumen breve del artículo para meta-descripción y feeds (opcional). idioma: Código del idioma ('es' o 'en') para Polylang (opcional). post_traduccion_id: ID del post en el otro idioma para vincularlos como traducciones (opcional). post_id: ID del post existente a actualizar (si se omite, crea un post nuevo).

Returns: Confirmación con ID del post, título, estado y enlaces directos de previsualización y edición.

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": {
      "titulo": "<titulo>",
      "contenido_html": "<contenido_html>"
    },
    "name": "publicar_borrador_wp"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNo
idiomaNo
tituloYes
post_idNo
extractoNo
etiquetasNo
categoriasNo
contenido_htmlYes
imagen_portada_idNo
post_traduccion_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations supplied, the description has to carry the behavioral load, and it does disclose the key trait that output is always 'draft' (not published) plus a 'Returns' section describing the confirmation payload. It omits what happens to existing fields when post_id is supplied (merge vs overwrite), whether the operation is reversible, and any auth/permission requirements — significant gaps for a write tool.

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?

The first sentence front-loads the purpose, a second sentence lists the supported capabilities, and the Args/Returns blocks are compact and skimmable. Because the schema carries no per-parameter descriptions, the Args block is not redundant — it is the only source of parameter meaning.

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 10-parameter mutation tool, the definition covers what each input means, the create/update branch, the Polylang language linkage, and confirms a draft-state outcome; the output schema handles return values. The remaining shortfall is contextual — no permission requirements and no differentiation from the overlapping sibling post tools.

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: all ten parameters are explained, with concrete value formats ([132, 137] for categories, 'es'/'en' for idioma, an example slug) and the create-vs-update semantics of post_id. Minor gaps remain, such as whether slug is auto-derived and how categories/etiquetas interact with existing ones.

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 opening sentence gives a specific verb plus resource ('Crea un nuevo post o actualiza uno existente en WordPress en estado draft') and enumerates the supported fields, so the scope is unambiguous. It does not, however, distinguish itself from siblings like 'actualizar_post' or 'gestionar_post', which appear to overlap on the update path.

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 post_id note ('si se omite, crea un post nuevo') and by the workflow hint that imagen_portada_id comes from 'subir_imagen_portada'. There is no explicit statement of when to prefer this tool over 'actualizar_post' or 'gestionar_post', nor any prerequisite or exclusion.

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