Skip to main content
Glama

pbs_job_delete

Delete a PBS scheduled job by job type and ID. Dry-run generates a plan; set confirm to true to remove the schedule without deleting backup data.

Instructions

MUTATION: delete a PBS scheduled job. job_type = sync|verify|prune. Dry-run by default — the PLAN captures current config (no UNDO primitive; re-create with pbs_job_create to restore the schedule). confirm=True to execute and returns synchronously (no task UPID). Schedule removed, backup data NOT deleted. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYesID of the PBS scheduled job to delete.
confirmNoGate: false returns a dry-run PLAN, true executes the deletion.
job_typeYesPBS job type: sync | verify | prune.
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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, but description fully discloses mutation nature, dry-run behavior, synchronous execution, no UNDO, backup data retention policy, and configuration needs.

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?

Single well-structured paragraph with critical information front-loaded: mutation type, dry-run, execution, side effects, prerequisites. No wasted words.

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?

Covers essential aspects: operation, dry-run, confirmation, backup data persistence, config needs. Lacks error handling details but sufficient given output schema existence.

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%, but description adds value by explaining job_type allowed values, confirm as dry-run gate, and proximo_target for multi-target config, exceeding bare schema info.

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?

Description clearly states it deletes a PBS scheduled job, specifies job_type values (sync|verify|prune), and distinguishes from sibling tools like pbs_job_create and pbs_job_update.

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?

Explains dry-run default with confirm gate, mentions alternative pbs_job_create for restoration, and notes config requirements. Provides clear context but no explicit exclusions for when not to use.

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