Skip to main content
Glama
WordPress MCP Server

WordPress MCP Server

by ernestoh0183

actualizar_post

Update specific fields of an existing WordPress post by ID, including title, content, excerpt, slug, featured image, categories, tags, and status, to revise only what changed.

Instructions

Actualiza atributos específicos de un post existente en WordPress (título, contenido, extracto, slug, portada, categorías, etiquetas o estado).

Args: post_id: ID del post a modificar en WordPress. titulo: Nuevo título (opcional). contenido_html: Nuevo cuerpo en HTML (opcional). extracto: Nuevo extracto descriptivo (opcional). slug: Nuevo slug para la URL (opcional). imagen_portada_id: Media ID de la imagen destacada (opcional). categorias: Lista de IDs de categorías a asignar (opcional). etiquetas: Lista de IDs de etiquetas a asignar (opcional). estado: 'draft', 'publish', 'pending', etc. (opcional).

Returns: Confirmación de los campos actualizados y enlace de la publicació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": {
      "post_id": "<post_id>"
    },
    "name": "actualizar_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNo
estadoNo
tituloNo
post_idYes
extractoNo
etiquetasNo
categoriasNo
contenido_htmlNo
imagen_portada_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose the useful partial-update semantic ("atributos específicos" = only the provided fields change) plus the shape of the response. It says nothing about permissions, side effects such as revision creation or cache invalidation, or whether changing estado to 'publish' has publishing consequences, which are important for a mutation tool.

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 purpose sentence followed by clean Args/Returns blocks, so an agent can scan it quickly. Repetition of "(opcional)" eight times is redundant given the schema's nullable defaults, but it costs little and reinforces which fields are safe to omit.

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?

An output schema exists, so the Returns line is a bonus rather than a necessity, and all nine parameters are covered, which is adequate for a nine-parameter mutation. What is missing is behavioral context that structured fields do not provide: permission requirements, side effects, and how partial updates interact with existing content, which matters given the absence of annotations.

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 nine parameters are explained in the Args block, including that post_id identifies the target, that imagen_portada_id is a Media ID, that categorias/etiquetas are lists of IDs, and it surfaces the meaningful estado values ('draft', 'publish', 'pending'). It is only a gloss on each field rather than deeper constraints (e.g., whether contenido_html replaces the full body).

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 ("Actualiza atributos específicos de un post existente en WordPress") and enumerates the mutable fields (título, contenido, extracto, slug, portada, categorías, etiquetas, estado), so an agent knows exactly what the tool changes. It does not, however, contrast itself with the sibling gestionar_post, so the reader must infer the boundary.

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 explicit when-to-use guidance: nothing says when to prefer this over gestionar_post or publicar_borrador_wp, and no prerequisites (authentication, capability requirements, need for an existing post ID beyond the schema) are mentioned. The only implied usage is that at least one optional field must be supplied alongside post_id, which the reader has to deduce.

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