Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_toggle_maintenance_mode

Activate or deactivate maintenance mode for a WordPress site to temporarily restrict access during updates or maintenance.

Instructions

Toggle maintenance mode for a site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
enabledYes

Implementation Reference

  • The handler function for the pressable_toggle_maintenance_mode tool which makes a POST request to toggle maintenance mode.
    handler: async (args) => {
        return await api.post(`/sites/${args.id}/maintenance-mode`, { enabled: args.enabled });
    }
  • The input schema for the pressable_toggle_maintenance_mode tool defining the expected 'id' and 'enabled' arguments.
    inputSchema: {
        type: 'object',
        properties: {
            id: { type: 'string' },
            enabled: { type: 'boolean' }
        },
        required: ['id', 'enabled']
    },
  • tools/sites.js:122-135 (registration)
    The full tool definition and registration for pressable_toggle_maintenance_mode in tools/sites.js.
        name: 'pressable_toggle_maintenance_mode',
        description: 'Toggle maintenance mode for a site.',
        inputSchema: {
            type: 'object',
            properties: {
                id: { type: 'string' },
                enabled: { type: 'boolean' }
            },
            required: ['id', 'enabled']
        },
        handler: async (args) => {
            return await api.post(`/sites/${args.id}/maintenance-mode`, { enabled: args.enabled });
        }
    },
Behavior2/5

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

With zero annotations provided, the description carries the full disclosure burden but fails to state what maintenance mode actually does (e.g., shows a maintenance page to visitors), whether changes are immediate, or if the operation is reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely brief at six words with no structural waste, but the brevity becomes a liability given the lack of supporting documentation in schema or annotations. Single sentence is front-loaded but underspecified.

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?

For a 2-parameter boolean toggle with no output schema and zero annotations, the description covers only the bare minimum. Critical gaps remain regarding parameter specifics, maintenance mode behavior, and operational consequences.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage, requiring the description to compensate, yet it provides no parameter documentation. It implicitly suggests 'id' is a site identifier via 'for a site', but does not explain that 'enabled' controls the on/off state of maintenance mode.

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?

States a clear verb (Toggle) + specific resource (maintenance mode) + scope (site). While it doesn't explicitly differentiate from similar siblings like pressable_disable_site, 'maintenance mode' implies a specific WordPress feature distinct from site suspension.

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 (e.g., disable_site), no mention of prerequisites, and no warnings about impacts on site visitors during maintenance mode.

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