Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

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

  • tools/sites.js:66-78 (handler)
    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`);
    }
},

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action 'disable' without explaining side effects, reversibility, permissions required, or impact on the site. This is insufficient for a mutating operation.

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 concise sentence with zero wasted words. However, it is extremely terse and lacks supportive context, so it does not fully earn its place as an informative description, though it is structurally efficient.

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?

The tool is a mutation with no annotations and no output schema. The description does not explain return values, side effects, or reversibility, and the single parameter is not elaborated. The description is inadequate for a mutating tool, leaving the agent without critical operational context.

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 covers 100% of parameters with a clear description for 'id' ('The site ID or name'), so the tool description adds no additional parameter meaning. Baseline of 3 is appropriate given the schema does the heavy lifting.

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 clear verb 'disable' and resource 'a specific site', making the purpose immediately understandable. It is distinguishable from sibling tools like pressable_enable_site and pressable_delete_site, though it does not elaborate on what 'disable' entails.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention prerequisites, typical scenarios, or mention the opposite tool pressable_enable_site. This leaves the agent without context for appropriate usage.

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