Skip to main content
Glama
PCWProps

Pressable MCP Server

by PCWProps
OverviewSchemaRelated ServersScoreDiscussions
JavaScript

pressable_list_backups

Retrieve a list of available backups for a WordPress site to restore previous versions or recover data.

Instructions

Get a list of backups for a specific site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

Implementation Reference

  • tools/backups.js:12-14 (handler)
    The handler function for 'pressable_list_backups' which calls the API to list backups for a site.
    handler: async (args) => {
    return await api.get(`/sites/${args.id}/backups`);
}
  • tools/backups.js:7-11 (schema)
    The input schema for 'pressable_list_backups'.
    inputSchema: {
    type: 'object',
    properties: { id: { type: 'string' } },
    required: ['id']
},
  • tools/backups.js:4-15 (registration)
    The registration object for 'pressable_list_backups'.
    {
    name: 'pressable_list_backups',
    description: 'Get a list of backups for a specific site.',
    inputSchema: {
        type: 'object',
        properties: { id: { type: 'string' } },
        required: ['id']
    },
    handler: async (args) => {
        return await api.get(`/sites/${args.id}/backups`);
    }
},

Tool Definition Quality

C2.6/5.0
Behavior2/5

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

No annotations provided, so the description carries full burden for behavioral disclosure. It does not specify return format, pagination behavior, filtering capabilities, or whether the operation is read-only (though implied by 'Get'). Missing critical context given zero annotation coverage.

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?

Single sentence of appropriate length, but offers minimal informational value beyond restating the tool name. Front-loaded but wasteful in that it could have incorporated parameter or behavioral details without sacrificing brevity.

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 the existence of ambiguous sibling tools and complete lack of parameter schema documentation, the description is insufficient. A complete description should clarify the relationship to `pressable_list_site_backups_by_type` and explicitly document the required 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 has 0% description coverage (the 'id' parameter is undocumented). While the description mentions 'specific site' implying the ID refers to a site identifier, it does not explicitly document the parameter name, type constraints, or expected format (e.g., numeric vs string site ID).

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 (Get/List) and resource (backups) with scope (specific site). However, fails to distinguish from the sibling tool `pressable_list_site_backups_by_type`, which creates ambiguity about whether this returns all backups or a subset.

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 `pressable_list_site_backups_by_type` or other backup-related tools like `pressable_create_on_demand_backup`. No prerequisites or exclusion criteria mentioned.

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