Skip to main content
Glama
WordPress MCP Server

WordPress MCP Server

by ernestoh0183

revisar_plugins

Retrieves all installed WordPress plugins with activation status and version, and optionally checks WordPress.org for available updates to help audit site plugins.

Instructions

Obtiene la lista completa de plugins instalados en WordPress, su estado (activo/inactivo), versión actual, y opcionalmente verifica si hay actualizaciones en WordPress.org.

Args: verificar_actualizaciones: Si es True, consulta el repositorio oficial de WordPress.org para ver si la versión instalada está actualizada.

Returns: Reporte consolidado de todos los plugins instalados.

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

Input Schema

NameRequiredDescriptionDefault
verificar_actualizacionesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/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 burden. It does add real behavioral context: the tool is a read operation and the optional flag triggers an external query to WordPress.org (implying network latency and possible failure). However, it does not state permission requirements, whether the call is safe/idempotent, or what happens if the repository is unreachable.

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 core purpose, then a clean Args/Returns structure. Slightly verbose in restating 'plugins instalados' across sections, but no sentence is wasted.

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?

An output schema exists, so the description need not enumerate return fields, and it still summarizes the result as a consolidated report. For a one-parameter read tool this is nearly complete; only permission and failure-mode context is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 explain the single parameter's meaning and effect in the Args block. That said, it adds no detail on cost, latency, or failure behavior of enabling the check, so it is adequate rather than rich.

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 ('Obtiene la lista completa de plugins instalados') plus the data returned (estado, versión) and the optional update check. It is clearly a read/inspection tool, which implicitly separates it from the mutation-oriented sibling 'administrar_plugin', but it never names or contrasts with any sibling explicitly.

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 only implied: the description makes clear this is for inspecting installed plugins, and the optional flag hints at when to enable the extra check. There is no explicit when-to-use/when-not guidance and no mention of when to prefer 'administrar_plugin' for changes instead.

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