Skip to main content
Glama
WordPress MCP Server

WordPress MCP Server

by ernestoh0183

leer_contexto_blog

Retrieves recent published blog posts in plain text so agents can understand editorial tone, style, and topics and avoid duplicate content, with optional language filtering (es/en).

Instructions

Obtiene los artículos publicados más recientes del blog en texto plano.

Permite al agente comprender el tono editorial, estilo y temas recientemente cubiertos para evitar contenido duplicado. Soporta filtrado por idioma (es/en).

Args: limite: Cantidad de artículos a consultar (por defecto 5, máx 20). idioma: Código de idioma opcional según Polylang ('es' para español, 'en' para inglés).

Returns: Resumen estructurado con ID, fecha, título, link y extracto de cada publicación.

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": "leer_contexto_blog"
  }
}

Input Schema

NameRequiredDescriptionDefault
idiomaNo
limiteNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the burden; it discloses that results are limited to published posts, returned as plain text, and filterable by language, which implies a read-only operation. It omits permission requirements, pagination behavior, and what happens when no posts exist, so behavioral coverage is only partial.

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?

Well front-loaded: purpose sentence, then the value proposition, then Args/Returns sections. The language-filter sentence in the body restates the Args entry for idioma, which is mild duplication but the description stays short and scannable.

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 two-optional-parameter read tool with an output schema, this is nearly complete: input constraints are enumerated and the return shape is summarized. The only gaps are operational context such as error behavior or whether drafts are excluded beyond 'publicados'.

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 both parameters are undocumented in the schema, but the description compensates: it gives limite's default (5) and maximum (20), and supplies the accepted idioma values ('es'/'en') under Polylang, which the schema only types as a nullable string. Only the fact that idioma is optional-by-default is somewhat redundant.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first line states a specific verb and resource ('Obtiene los artículos publicados más recientes del blog') plus the output format ('texto plano'). It also names the agent-facing intent (understand tone, style and recent topics to avoid duplicate content), which distinguishes it from the mutation-oriented siblings such as gestionar_post or actualizar_post.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear trigger for use: consult recent posts before writing to avoid duplicating topics. It does not name an explicit alternative or exclusion (e.g., how it relates to gestionar_post for reading a single post), so it falls short of full when/when-not guidance.

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