pocketbase-mcp

Create backup

create_backup

Create a zip snapshot of the PocketBase database and storage. Specify an optional backup filename, or let it auto-generate a timestamped name. Requires superuser access.

Instructions

Create a new backup (zip snapshot of the database and storage). If basename is omitted, PocketBase auto-generates a timestamped name. Returns the backup name. Superuser only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_backup"
  }
}

Input Schema

Name	Required	Description	Default
`basename`	No	Optional backup file name, e.g. 'pb_backup_2024.zip' (auto-generated if omitted).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 6, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations to fall back on, the description carries the full behavioral burden and does so well. It discloses that the backup is a zip snapshot of database and storage, that omitting basename yields a timestamped name, that the backup name is returned, and that superuser authorization is required.

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 four short sentences, front-loaded with the core action, and every sentence adds meaningful functional content. There is no redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with one optional parameter and no output schema, the description provides all essential context: what it does, what it contains, how the parameter behaves, what is returned, and who can call it. An agent can invoke this tool correctly without additional information.

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

Parameters4/5

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

Schema coverage is 100% already, so the baseline is 3. The description goes beyond the schema by specifying that an omitted basename produces a timestamped name and that the tool returns the backup name, adding useful semantic detail for the single optional parameter.

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 a specific verb ('Create'), a clear resource ('a new backup'), and explains what it is ('zip snapshot of the database and storage'). It distinguishes itself from sibling backup tools like list_backups, restore_backup, upload_backup, and delete_backup by emphasizing that it creates a new backup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description makes it clear this is the tool to use for creating a new backup and even notes the 'Superuser only' access restriction. However, it does not explicitly name alternatives or mention when not to use it, though the context is already strong enough for an agent to route correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server