Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Cache purge

wordpress_cache_purge
Destructive

Purge WordPress caches through the airano-mcp-bridge plugin by auto-detecting active cache plugins to clear page, site-wide, or object cache.

Instructions

[UNIFIED] Purge WordPress caches on the WordPress site via the airano-mcp-bridge companion plugin (v2.4.0+). Auto-detects active cache plugins (LiteSpeed, WP Rocket, W3 Total Cache, WP Super Cache, WP Fastest Cache, SiteGround Optimizer) and calls each one's purge API when scope is page or all. Flushes the object cache when scope is object or all. Requires manage_options on the calling application password.

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": {
      "site": "<site>"
    },
    "name": "wordpress_cache_purge"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
scopeNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.14.0
    • addedInput schema / properties / scope
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": "all"
+}
  2. Addedv3.13.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is covered. The description adds substantive context beyond that: the required companion plugin version, the auto-detection of six cache plugins and per-plugin API calls, and the manage_options authorization requirement.

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?

Three front-loaded sentences: identity, behavior per scope, then prerequisites. Dense with facts and free of filler, though the plugin list could be compressed without losing routing value.

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 2-parameter destructive mutation with no output schema, it covers prerequisites, side effects and scope behavior well. It stops short of saying what the call returns or how the caller confirms the purge succeeded, which matters for a destructive operation.

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 coverage is 0%, so the description must carry parameter meaning, and it partially does by introducing the scope values page, object and all and tying each to a behavior. It never explains what "page" scope targets when no page identifier parameter exists, and gives no format for the required site parameter (URL, slug, or ID).

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 gives a specific verb+resource (purge WordPress caches) and even names the mechanism (airano-mcp-bridge companion plugin) and the cache plugins covered. It does not differentiate from the close sibling wordpress_wp_cache_flush or cloudflare_purge_cache, so an agent must guess which purge tool applies.

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?

It implies usage through the scope semantics (page/all purges plugin caches; object/all flushes the object cache), which is genuinely useful routing logic. But there is no explicit when-to-use vs. wordpress_wp_cache_flush or cloudflare_purge_cache, and no statement of when not to purge.

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

Deploy Server

Other Tools