Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp transient list

wordpress_wp_transient_list
Read-only

List WordPress transients with names, type, and expiration metadata through the companion plugin without reading transient values.

Instructions

[UNIFIED] List WordPress transients through the companion plugin. Returns names, type, and expiration metadata without reading transient values.

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

Input Schema

NameRequiredDescriptionDefault
siteYes
limitNo
include_site_transientsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.14.0
    • addedInput schema / properties / include_site_transients
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": true
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": 100
+}
  2. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observedv3.4.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine behavior beyond that: what is returned (names, type, expiration metadata) and, importantly, that transient values are not read, which tells the agent there is no payload exposure. It omits pagination behavior around limit and what happens when the companion plugin is unavailable.

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 tightly written sentences with zero waste; the core action is front-loaded and the return/scope qualification follows immediately.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Purpose and return shape are adequately covered for a three-parameter read tool with no output schema, but parameter meaning is entirely absent given 0% schema description coverage. An agent knows what the tool does but not how to drive its filters correctly.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and none of the three parameters (site, limit, include_site_transients) are explained in the description. 'include_site_transients' in particular is opaque — the description never says what site transients are or why one would exclude them — so the description fails to compensate for the coverage gap.

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 ('List WordPress transients') and clarifies scope with 'Returns names, type, and expiration metadata without reading transient values.' An agent can distinguish this read-only listing from the delete/flush siblings by the verb alone, though no sibling is named 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: 'without reading transient values' suggests reaching for this tool when only metadata is needed, and 'through the companion plugin' hints at a prerequisite. There is no explicit when-to-use/when-not guidance or pointer to the delete_all or flush alternatives.

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