Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Transient flush

wordpress_transient_flush
Destructive

Clear WordPress transients by scope—expired, all, or matching patterns—via the airano-mcp-bridge companion plugin; optionally purge multisite site transients.

Instructions

[UNIFIED] Flush WordPress transients via the airano-mcp-bridge companion plugin (v2.5.0+). Scopes: 'expired' (default, delete_expired_transients), 'all' (every transient), 'pattern' (shell glob like 'rank_math_*'). On multisite, include_site_transients=true also purges site_transient* rows. Requires manage_options.

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_transient_flush"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
scopeNo
patternNo
include_site_transientsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.13.1

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the operation as destructive and non-readonly. The description adds useful context beyond annotations: it requires manage_options, the default scope only deletes expired transients, and multisite can include site transients when requested.

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?

The description is front-loaded, uses short scoped examples, and avoids unnecessary repetition. The plugin version and unified tag add minor noise but are plausibly relevant for compatibility.

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 four-parameter destructive tool with no output schema, it covers the important behavioral context: permissions, scope semantics, pattern matching, and multisite handling. The main gap is that the required site parameter is never explained.

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%, so the description must carry parameter meaning, and it does for scope, pattern, and include_site_transients. It defines the three scope values, gives a glob example for pattern, and explains the multisite effect, though it does not describe the required site parameter.

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: flushing WordPress transients. It also names the supported scope modes and the companion plugin, making the operation clear, though it does not explicitly differentiate this tool from similar transient-delete or cache-flush siblings.

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 explains the default scope and what each scope does, which gives implied usage guidance for parameter choices. However, it does not say when to use this tool instead of similar siblings such as transient delete-all or cache flush, nor does it provide exclusions.

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