Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

pressable_purge_edge_cache

Clear cached content from edge servers for a WordPress site to ensure visitors see the most recent version of your pages.

Instructions

Purge the edge cache for a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSite ID or name

Implementation Reference

  • tools/cache.js:24-26 (handler)
    The handler function that executes the purge edge cache operation by calling the API.
    handler: async (args) => {
    return await api.post(`/sites/${args.id}/edge-cache/purge`);
}
  • tools/cache.js:19-23 (schema)
    Input schema definition for the pressable_purge_edge_cache tool.
    inputSchema: {
    type: 'object',
    properties: { id: { type: 'string', description: 'Site ID or name' } },
    required: ['id']
},
  • tools/cache.js:16-27 (registration)
    The registration object for the pressable_purge_edge_cache tool.
    {
    name: 'pressable_purge_edge_cache',
    description: 'Purge the edge cache for a specific site.',
    inputSchema: {
        type: 'object',
        properties: { id: { type: 'string', description: 'Site ID or name' } },
        required: ['id']
    },
    handler: async (args) => {
        return await api.post(`/sites/${args.id}/edge-cache/purge`);
    }
},

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations are provided, and the description adds no behavioral context beyond the action itself. It does not disclose whether the purge is immediate or asynchronous, if it returns status information, rate limits, or whether the operation is idempotent.

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?

Single sentence, front-loaded with the action verb, and contains no redundant or wasted words. Appropriate length for the tool's complexity.

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?

Adequate for a single-parameter mutation tool with no output schema, though given the presence of similar cache-related siblings, additional context about edge cache behavior or success indicators would strengthen completeness.

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 100% schema description coverage for the single 'id' parameter, the schema already documents the input requirements. The description mentions 'for a specific site' which aligns with the parameter semantics but adds no additional syntactic or format guidance beyond the schema.

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 a specific verb ('Purge') and resource ('edge cache') with clear scope ('for a specific site'). It implicitly distinguishes from siblings like pressable_flush_object_cache by specifying 'edge' cache, though it does not explicitly contrast these similar operations.

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?

Provides no guidance on when to use this tool versus alternatives like pressable_flush_object_cache or pressable_toggle_edge_cache, nor does it mention prerequisites (e.g., whether edge cache must be enabled first).

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