Skip to main content
Glama
WordPress MCP Server

WordPress MCP Server

by ernestoh0183

subir_imagen_portada

Upload an image from a local path, public URL, or Base64 string to the WordPress media library for use as a featured image.

Instructions

Sube una imagen a la biblioteca de medios de WordPress para ser usada como portada.

El argumento 'origen_imagen' puede ser:

  1. Una ruta a un archivo local en disco (ej. 'C:\imagenes\portada.jpg').

  2. Una URL pública directa a la imagen (ej. 'https://.../imagen.jpg').

  3. Una cadena codificada en Base64.

Args: origen_imagen: Ruta local, URL HTTP/HTTPS o string en base64 de la imagen. nombre_archivo: Nombre con el que se guardará en WordPress (opcional, ej. 'ia-portada.jpg'). texto_alt: Texto alternativo para SEO y accesibilidad (opcional).

Returns: Diccionario con el resultado, ID asignado en WordPress y URL pública: {"status": "success", "id": 1045, "url": "https://..."}

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": {
      "origen_imagen": "<origen_imagen>"
    },
    "name": "subir_imagen_portada"
  }
}

Input Schema

NameRequiredDescriptionDefault
texto_altNo
origen_imagenYes
nombre_archivoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/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 behavioral burden; it does disclose that this is a write into the WordPress media library and what the return payload looks like. It omits important traits: required credentials/permissions, size or MIME restrictions, and what happens on name collision (overwrite vs. dedupe) — all material for a mutating upload.

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 with the purpose, then a numbered list of accepted input forms and a compact Args/Returns block; an agent can scan it quickly. The numbered list and the Args entry for origen_imagen repeat the same three forms, which is slight redundancy.

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?

There is no output schema, and the description compensates by documenting the returned dictionary keys (status, id, url). With three parameters, one required, it covers inputs and outputs adequately; only failure behavior and image constraints are unaddressed.

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%, and the description compensates well by enumerating the three accepted forms of origen_imagen with concrete examples and by clarifying that nombre_archivo and texto_alt are optional and what each is for. Minor gaps remain, such as whether base64 needs a data-URI prefix or whether the file extension in nombre_archivo must match the image type.

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 description states a specific verb and resource ('Sube una imagen a la biblioteca de medios de WordPress') plus the intended use ('para ser usada como portada'), which is unambiguous. It stops short of naming a sibling upload or media tool, so the agent gets no explicit differentiation from related WordPress operations.

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 stated goal (obtain a media-library image usable as a featured image), and the format variants of origen_imagen are spelled out. There is no explicit when-to-use/when-not guidance, no prerequisites, and no mention of what other tool to call to attach the returned ID to a post.

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