Veeam VBR v13 MCP Server

GetBackupObjectsWithFiltering

Retrieve VMs and servers from a specific Veeam backup using filtering options to find relevant objects quickly.

Instructions

Get objects (VMs, servers) contained in a specific backup.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

Name	Required	Description	Default
`id`	Yes
`skip`	No
`limit`	No
`nameFilter`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 21, 2026

TDQS

C2.8/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves objects but lacks details on permissions, rate limits, pagination (implied by skip/limit parameters but not explained), or response format. This is inadequate for a tool with multiple parameters and no output schema.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded and appropriately sized for its content.

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

Completeness2/5

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

Given the tool has 4 parameters (1 required), 0% schema coverage, no annotations, and no output schema, the description is insufficient. It lacks details on parameter usage, behavioral traits, and output, making it incomplete for effective agent invocation.

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

Parameters2/5

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

Schema description coverage is 0%, so the schema provides no parameter details. The description mentions filtering by name ('nameFilter') but does not explain the 'id' parameter (likely backup identifier), 'skip', or 'limit'. It partially compensates for the coverage gap but leaves key parameters undocumented.

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 clearly states the verb ('Get') and resource ('objects (VMs, servers) contained in a specific backup'), making the purpose explicit. However, it does not differentiate from sibling tools like 'GetAllBackupObjects' or 'GetBackupObject', which might retrieve similar data without filtering or with different scopes.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, such as 'GetAllBackupObjects' for unfiltered lists or 'GetBackupObject' for single objects. There is no mention of prerequisites, context, or exclusions, leaving usage ambiguous.

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

Deploy Server