Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

pressable_flush_object_cache

Clear cached data for a specific WordPress site to ensure updated content displays immediately.

Instructions

Flush the object cache for a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • tools/sites.js:117-119 (handler)
    The handler function for 'pressable_flush_object_cache' which calls the API to flush the cache.
    handler: async (args) => {
    return await api.post(`/sites/${args.id}/flush-object-cache`);
}
  • tools/sites.js:112-116 (schema)
    The input schema for 'pressable_flush_object_cache' requiring a site ID.
    inputSchema: {
    type: 'object',
    properties: { id: { type: 'string' } },
    required: ['id']
},
  • tools/sites.js:110-120 (registration)
    The registration object for the 'pressable_flush_object_cache' tool.
        name: 'pressable_flush_object_cache',
    description: 'Flush the object cache for a specific site.',
    inputSchema: {
        type: 'object',
        properties: { id: { type: 'string' } },
        required: ['id']
    },
    handler: async (args) => {
        return await api.post(`/sites/${args.id}/flush-object-cache`);
    }
},

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Flush' implies a destructive operation, the description fails to state that cached data will be permanently cleared, that this may cause temporary performance degradation, or whether the operation is synchronous.

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 a single sentence with no wasted words. It is appropriately front-loaded with the action verb, though its extreme brevity contributes to informational gaps in other dimensions.

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

Completeness2/5

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

Given zero annotations, no output schema, and a destructive operation with 0% parameter documentation, the description is insufficiently complete. It omits critical context about the nature of object caching, side effects, and expected outcomes.

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?

With 0% schema description coverage, the description partially compensates by referencing 'a specific site,' implying the 'id' parameter refers to a site identifier. However, it does not explicitly document the parameter, its format, or how to obtain valid IDs.

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 uses the specific verb 'Flush' and identifies the resource as 'object cache for a specific site.' It implicitly distinguishes from the sibling tool 'pressable_purge_edge_cache' by specifying 'object cache' versus edge caching, though it does not explicitly contrast the two.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives (like purging edge cache), nor does it mention prerequisites such as site ownership or when flushing is appropriate (e.g., after code deployments).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PCWProps/pressable-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server