Skip to main content
Glama
WordPress MCP Server

WordPress MCP Server

by ernestoh0183

actualizar_configuracion

Updates general WordPress settings—title, tagline, timezone, logo, and favicon—so you can change site identity and localization from one call.

Instructions

Actualiza opciones generales de WordPress (Título, Tagline, Zona Horaria, Logo o Favicon).

Args: titulo: Nuevo título para el blog (opcional). descripcion: Nuevo subtítulo o lema (tagline) del sitio (opcional). zona_horaria: Identificador de zona horaria (ej. 'America/Santiago') (opcional). site_logo_id: Media ID de la imagen para el logotipo oficial del sitio (opcional). site_icon_id: Media ID de la imagen para el icono/favicon del sitio (opcional).

Returns: Confirmación de las configuraciones modificadas.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "actualizar_configuracion"
  }
}

Input Schema

NameRequiredDescriptionDefault
tituloNo
descripcionNo
site_icon_idNo
site_logo_idNo
zona_horariaNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden: it never says that omitted optional fields are left unchanged, that the change is a persistent/irreversible site-wide mutation, or that admin-level permissions are required. It does mention a confirmation return, but since an output schema exists that information is largely redundant and does not compensate for the missing mutation semantics.

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 purpose sentence is front-loaded and the Args block maps one-to-one onto the five parameters, so scanning is easy. The repeated '(opcional)' on every entry is redundant with the schema's default=null and anyOf null typing, which is minor waste rather than a structural problem.

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 5-parameter, zero-annotation mutation tool, the description covers every parameter and names the return, and the output schema relieves it of explaining return values. However, it leaves out the partial-update contract (are unspecified settings preserved?) and the permission requirements, which an agent needs before invoking a site-wide settings change.

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 docstring must carry all parameter meaning, and it does: it clarifies that 'descripcion' is the site tagline (non-obvious from the field name), gives a concrete timezone format example ('America/Santiago'), and explains that site_logo_id/site_icon_id are Media IDs rather than URLs. It adds genuine meaning beyond the bare schema titles, though it omits any note on valid ranges or what happens when all five are null.

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 opciones generales de WordPress') and enumerates the concrete settings it touches (Título, Tagline, Zona Horaria, Logo, Favicon), which clearly distinguishes it from the read-only sibling obtener_configuraciones. It stops short of naming any sibling explicitly, so it stays at 4 rather than 5.

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 guidance on when to use this tool versus alternatives such as obtener_configuraciones (read) or gestionar_post, nor any stated prerequisites like administrator capabilities. Usage is only inferable from the tool name and the word 'Actualiza', which is the definition of implied-only guidance.

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