Skip to main content
Glama
WordPress MCP Server

WordPress MCP Server

by ernestoh0183

purgar_cache_sitio

Purges WP Super Cache, Docket Cache, and OPcache so content, menu, widget, and taxonomy updates appear immediately on the live WordPress site.

Instructions

Purga de inmediato las cachés del servidor (WP Super Cache, Docket Cache y OPcache) para que las publicaciones, cambios de menú, widgets y taxonomías se reflejen en el acto.

Returns: Confirmación de las cachés purgadas y timestamp.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/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 usefully discloses the scope of the operation (three named cache layers) and that the effect is immediate, but says nothing about required permissions, whether the purge is reversible or has performance impact, or how failures are reported.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and its scope, followed by the effect. Every clause earns its place and nothing is padded.

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 brief return note is a bonus rather than a requirement. For a zero-parameter cache purge the definition is nearly complete, with only permission and error behavior left unstated.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; the baseline of 4 applies. The description correctly implies a no-argument, fire-and-forget invocation.

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?

States a specific verb (purga) and resource (cachés del servidor) and enumerates the exact caches affected: WP Super Cache, Docket Cache and OPcache. No sibling tool in the catalog deals with caching, so the agent can identify this unambiguously.

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?

The description gives a clear usage context: call it so that posts, menu changes, widgets and taxonomies are reflected immediately. It does not state when NOT to use it or name alternatives, but for a zero-parameter maintenance action the trigger condition is clear enough.

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