Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_disable_site

Disable a specific WordPress site by ID or name to temporarily take it offline or prepare for maintenance using the Pressable API.

Instructions

Disable a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe site ID or name

Implementation Reference

  • The 'pressable_disable_site' tool is defined as an object within the 'siteTools' array in 'tools/sites.js'. The 'handler' property contains the asynchronous function that sends a POST request to the '/sites/${args.id}/disable' endpoint using the 'api' helper.
        name: 'pressable_disable_site',
        description: 'Disable a specific site.',
        inputSchema: {
            type: 'object',
            properties: {
                id: { type: 'string', description: 'The site ID or name' }
            },
            required: ['id']
        },
        handler: async (args) => {
            return await api.post(`/sites/${args.id}/disable`);
        }
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but fails to disclose if the action is reversible (likely yes, given pressable_enable_site exists), what visitors see when disabled, or whether data is preserved.

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?

Extremely concise at four words with no filler, though this brevity contributes to underspecification rather than efficient information density.

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 this is a state-changing mutation with multiple related sibling operations (enable, delete, maintenance mode), the single-sentence description insufficiently explains the disable state semantics or side effects.

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?

Input schema has 100% coverage with 'id' described as 'The site ID or name'. The description adds no additional parameter context, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

States the verb (disable) and resource (site) clearly, but does not distinguish from similar sibling tools like pressable_delete_site or pressable_enable_site, nor clarify whether 'disable' means offline, suspended, or maintenance mode.

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 pressable_delete_site (permanent removal) or pressable_toggle_maintenance_mode (temporary maintenance state), or prerequisites like requiring site ownership.

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