Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

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

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must carry behavioral transparency. It identifies the operation as 'Get' (implying a read), but does not disclose whether the URL expires, whether authentication is needed, or any side effects. This is minimal and adds little beyond the tool name.

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

Conciseness5/5

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

The description is a single, front-loaded sentence that directly states the action and target. No unnecessary words are present.

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 tool with no output schema, the description does not explain the return value's format or potential caveats (e.g., URL expiration). It lacks guidance on how the download URL should be consumed, making it incomplete for a straightforward tool.

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 does not elaborate on site_id or backup_id. While the parameter names are reasonably self-explanatory, the description adds no additional semantic context for constructing valid calls.

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

Purpose5/5

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

The description states the tool's function clearly: 'Get a download URL for a specific backup.' This uses a specific verb and resource, and it is distinct from sibling tools like list_backups or restore_site.

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 offers no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as obtaining a backup_id from list_backups. The context implies usage but provides no direct instruction.

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