Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_restore_site

Restore a WordPress site from backup by specifying site ID, filesystem, and database options. Use this tool to recover site data and configurations when needed.

Instructions

Restore a site from a backup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSite ID to restore
filesystem_idNo
database_idNo
restore_on_site_idNoOptional ID of site to restore onto

Implementation Reference

  • The handler function that executes the restore operation by making a POST request to the Pressable API.
    handler: async (args) => {
        const { id, ...restoreData } = args;
        return await api.post(`/sites/${id}/restores`, restoreData);
    }
  • The JSON schema defining the required and optional inputs for the pressable_restore_site tool.
    inputSchema: {
        type: 'object',
        properties: {
            id: { type: 'string', description: 'Site ID to restore' },
            filesystem_id: { type: 'integer' },
            database_id: { type: 'integer' },
            restore_on_site_id: { type: 'integer', description: 'Optional ID of site to restore onto' }
        },
        required: ['id']
    },
  • tools/backups.js:32-48 (registration)
    The complete tool definition object for pressable_restore_site, including name, description, schema, and handler.
        name: 'pressable_restore_site',
        description: 'Restore a site from a backup.',
        inputSchema: {
            type: 'object',
            properties: {
                id: { type: 'string', description: 'Site ID to restore' },
                filesystem_id: { type: 'integer' },
                database_id: { type: 'integer' },
                restore_on_site_id: { type: 'integer', description: 'Optional ID of site to restore onto' }
            },
            required: ['id']
        },
        handler: async (args) => {
            const { id, ...restoreData } = args;
            return await api.post(`/sites/${id}/restores`, restoreData);
        }
    },
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. While 'restore' implies a write operation, the description fails to clarify whether this is destructive (overwrites current site data), causes downtime, requires specific permissions, or how filesystem_id and database_id relate to backup components.

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?

The single five-word sentence is efficient but underspecified given the tool's complexity (4 parameters, optional cross-site restoration, destructive operation). It front-loads the action but wastes the opportunity to provide critical context in a compact way.

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 destructive operation with 4 parameters including optional cross-site targeting capabilities, no output schema, and zero annotations, the description is severely incomplete. It lacks essential context about backup component selection (filesystem vs database) and the implications of the restore_on_site_id parameter.

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 description coverage is 50% (filesystem_id and database_id lack descriptions). The description adds no information about these parameters, failing to explain that they likely reference backup IDs obtained from list_backups or list_site_backups_by_type, or that restore_on_site_id enables cross-site cloning.

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 'Restore a site from a backup' provides a clear verb (restore), resource (site), and scope (from backup). However, it misses the nuance that the tool can restore to a different target site (via restore_on_site_id) and doesn't differentiate from sibling tools like pressable_create_on_demand_backup or pressable_get_backup_download_url.

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?

The description provides no guidance on when to use this tool versus alternatives, prerequisites (e.g., needing backup IDs from list_backups), or warnings that this operation will overwrite existing site data. There is no mention of when restoration is appropriate or required preconditions.

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