Skip to main content
Glama

pbs_tape_backup_job_create

Create a tape backup job in Proxmox Backup Server with specified job ID, drive, media pool, and datastore. Plan first with dry-run mode, then confirm to execute.

Instructions

MUTATION: create a PBS tape backup job.

RISK_LOW: additive — no existing job/pool/drive config is affected. Dry-run by default (returns a PLAN); confirm=True executes (POST /config/tape-backup-job, synchronous — PBS returns null) and returns {"status": "ok", "result": None}. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nsNoNamespace to operate on.
poolYesMedia pool name (2-32 chars).
driveYesDrive identifier (3-32 chars).
storeYesDatastore name (3-32 chars).
job_idYesNew tape backup job ID (3-32 chars).
commentNoOptional comment (<=128 chars).
confirmNoFalse (default) returns a dry-run PLAN only; True executes the creation.
scheduleNoCalendar-event schedule string for automatic runs.
max_depthNoHow many namespace levels to operate on (0-7, default 7).
eject_mediaNoEject media upon job completion.
latest_onlyNoBack up latest snapshots only.
notify_userNoUser ID to notify (user@realm).
group_filterNoGroup filters, e.g. 'type:vm', 'group:GROUP', 'regex:RE', optionally prefixed 'exclude:'/'include:'.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.
worker_threadsNoNumber of worker threads (1-32, default 1).
export_media_setNoExport media set upon job completion.
notification_modeNo'legacy-sendmail' or 'notification-system' (default).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

The description fully discloses behavior: dry-run returns a PLAN, confirm=True executes and returns a specific success response, and it notes the synchronous nature and endpoint. Since no annotations are provided, the description carries the full burden and meets it excellently.

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 extremely concise, with only four lines covering purpose, risk, behavior, and prerequisites. Every sentence adds value, and the most critical info is front-loaded (MUTATION, create, RISK_LOW).

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

Completeness4/5

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

Given the complexity (17 parameters, 4 required, full schema, output schema exists), the description covers essential behavioral aspects: dry-run, execution, endpoint, sync, and config requirement. It lacks error case details, but output schema may cover that. Slightly more context on interaction with other tape components could help, but overall adequate.

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

Parameters3/5

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

Schema coverage is 100%, so parameters are well-documented in the schema. The description adds general context (e.g., dry-run, confirm) but doesn't provide additional meaning beyond what the schema already offers for individual parameters. Baseline of 3 is appropriate.

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 clearly states the action ('create a PBS tape backup job') and resource, differentiating it from sibling tools like pbs_tape_backup_job_delete, get, list, run, and update. The MUTATION label and risk level further clarify the purpose.

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 provides clear context on when to use: it's additive (no existing config affected), low risk, and includes a dry-run mode. It also mentions the need for PROXIMO_PBS_* config. It doesn't explicitly state when not to use, but the sibling tools imply alternatives.

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/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server