Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
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`);
    }
},

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Purge' implies a destructive action, but the description does not explain effects, reversibility, or any side effects. It adds no detail beyond the operation itself.

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?

The description is a single concise sentence that directly states the tool's function. Every word is purposeful, and the structure is front-loaded with the verb and target.

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?

The tool is simple with one parameter and no output schema, so the description is minimally adequate. However, it lacks any mention of prerequisites, edge cases, or what happens after the purge, which would be helpful for an agent to invoke it correctly. It meets the minimum viable bar but no more.

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?

The input schema provides a description for the id parameter ('Site ID or name'), giving 100% coverage. The tool description does not add additional meaning beyond what the schema already states, so the baseline of 3 applies.

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 clearly states the action ('Purge') and the resource ('edge cache for a specific site'), making the tool's purpose specific. However, it does not explicitly distinguish it from sibling tools like pressable_get_edge_cache_status or pressable_toggle_edge_cache, which are similarly scoped.

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?

No guidance is provided about when to use this tool versus alternatives. The description only states what it does, leaving the agent to infer usage from the tool name and sibling context. There are no exclusions or explicit references to other cache-related tools.

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