Skip to main content
Glama

vspc_list_jobs

Read-onlyIdempotent

List Veeam Backup & Replication jobs across managed clients and filter by company, backup server, status, or name to review latest results, run times, and failure messages.

Instructions

Jobs on managed Veeam Backup & Replication servers (VM backup, replication, backup copy, tape, file share, agent jobs managed by VBR): latest result, last run and end, duration, destination, failure message. Filter by company, backup server, latest result and name. For "what failed recently" across all clients, use vspc_list_failed_jobs or vspc_failed_jobs_summary.

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": "vspc_list_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOnly items whose name contains this text (case-insensitive).
limitNoPage size (VSPC maximum 500).
offsetNoItems to skip (for the next page).
companyNoCompany (client) as its VSPC UID or its name (exact, or a unique part of it). Leave out for every company.
enabledNotrue: only jobs whose schedule is enabled; false: only disabled ones.
statusesNoOnly jobs whose latest session has one of these results, e.g. ["Failed","Warning"].
backup_server_uidNoOnly jobs on this backup server (UID from vspc_list_backup_servers).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already carry the safety profile (readOnlyHint, idempotentHint, non-destructive), so the bar is lower. The description adds real value by telling the agent what each record contains, which matters because there is no output schema. It is silent on pagination behavior and how deep result sets are capped, which is minor.

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?

The returned fields are listed up front and the sibling routing sits at the end where it belongs. Three sentences with essentially no filler. The parenthetical job-type list is a bit dense but it is load-bearing scoping information.

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?

For a 7-parameter, optional-everything list tool with no output schema, the description covers what is needed: the resource, the returned fields, the filters, and the alternative for failure triage. Pagination is delegated to the schema, which is reasonable but does mean the description does not fully close the loop.

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 the schema already documents all 7 parameters with types, bounds, and examples. The description echoes four filter dimensions (company, backup server, latest result, name) but adds nothing beyond that, and omits enabled, limit, and offset. The baseline of 3 is warranted.

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?

The description states a concrete resource (jobs on managed Veeam Backup & Replication servers) and enumerates the fields returned: latest result, last run and end, duration, destination, failure message. That set of returned fields is what really distinguishes it from siblings like vspc_list_agent_jobs. However, it never draws a clean line between 'agent jobs managed by VBR' and the advertised sibling vspc_list_agent_jobs, leaving a small ambiguity.

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?

A clear conditional pointer is given: for 'what failed recently' across all clients, use vspc_list_failed_jobs or vspc_failed_jobs_summary. The filter list also tells the agent how to narrow the result. The missing piece is an explicit exclusion against vspc_list_agent_jobs, the sibling closest to this one.

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