Skip to main content
Glama

pve_tasks_list

List recent tasks on a Proxmox node. Filter by VMID, task type, status, or only errors. Returns up to 1000 results.

Instructions

READ-ONLY: list recent tasks on a node. limit max 1000 (higher is truncated; 0 or negative is rejected). No state change; returns a list of task dicts. Use pve_task_log for a task's full log.

Caveat: this is a windowed, per-node slice — node defaults to the configured node, and only the limit most-recent tasks return. A task on another node or outside the window is absent without being dead. Never conclude a backup failed from absence here — verify against pve_backup_list or pbs_snapshots_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoNode to list tasks from; defaults to the configured node.
vmidNoOptional VMID/CTID to filter tasks to a single guest.
limitNoMax number of most-recent tasks to return, max 1000 (0 or negative is rejected).
errorsNoIf True, only return tasks that ended in error.
typefilterNoOptional task-type filter, e.g. 'vzdump', 'qmigrate' (PVE task type string).
statusfilterNoOptional status filter, e.g. 'running', 'stopped'.
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
Behavior4/5

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

Declares READ-ONLY and no state change. Describes limit truncation/rejection, windowed per-node slice. Lacks auth or rate limit details, but sufficient for a read-only list tool.

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

Conciseness4/5

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

Well-structured with purpose first, then caveats. Some redundancy (e.g., limit details mentioned twice), but overall efficient and front-loaded.

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?

Given output schema exists, no need for return value details. Covers all aspects: purpose, parameters, behavior, limitations, and alternatives. Complete for a list tool.

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 baseline is 3. Description adds minimal context beyond schema, like 'node defaults to configured node' and 'only the limit most-recent tasks return', but not substantial extra meaning.

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 it lists recent tasks on a node (verb+resource+scope). It distinguishes from pve_task_log for full logs and pve_backup_list/pbs_snapshots_list for backup verification.

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

Usage Guidelines5/5

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

Explicitly states when to use (list recent tasks) and when not to (do not conclude backup failure from absence). Provides caveats about per-node windowing and limit behavior.

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