Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps

pressable_get_backup_download_url

Retrieve a downloadable URL for a specific site backup to access or restore data. Provide the site ID and backup ID to generate the secure download link.

Instructions

Get a download URL for a specific backup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
site_idYes
backup_idYes

Implementation Reference

  • The registration and handler implementation for the 'pressable_get_backup_download_url' tool.
        name: 'pressable_get_backup_download_url',
        description: 'Get a download URL for a specific backup.',
        inputSchema: {
            type: 'object',
            properties: {
                site_id: { type: 'string' },
                backup_id: { type: 'integer' }
            },
            required: ['site_id', 'backup_id']
        },
        handler: async (args) => {
            return await api.get(`/sites/${args.site_id}/backups/${args.backup_id}`);
        }
    }
Behavior2/5

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

With no annotations provided, the description carries full disclosure burden but omits critical behavioral details: whether the URL is time-limited/expiring, whether generating the URL triggers audit logs or rate limits, and what data structure is returned (string vs object with URL field).

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 sentence is front-loaded with the verb and contains no redundant text. However, extreme brevity results in underspecification for a tool with zero schema documentation; an additional sentence explaining parameters or URL expiration would add value without sacrificing clarity.

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 zero schema coverage, no annotations, and no output schema, the description is incomplete. It omits the temporary/ephemeral nature typical of backup download URLs, the relationship between site_id and backup_id (hierarchical dependency), and the expected return structure.

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 0% and the description fails to compensate. While 'specific backup' implicitly references backup_id, site_id is completely undocumented. No explanation of parameter formats, valid ranges, or where to obtain valid values (e.g., that backup_id comes from pressable_list_backups).

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 uses a specific verb ('Get') and resource ('download URL for a specific backup') clearly stating the tool's function. However, it fails to mention the site-specific context (site_id parameter) or distinguish from sibling pressable_restore_site, which also involves backups but performs restoration rather than providing a download link.

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 provided on when to use this versus alternatives like pressable_list_backups (which must be called first to obtain the backup_id), or prerequisites such as needing an existing backup. The description lacks explicit workflow context.

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