Skip to main content
Glama
lazyants

hetzner-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Storage Box Snapshots

hetzner_list_storage_box_snapshots
Read-onlyIdempotent

List snapshots for a Hetzner Storage Box by ID, with optional filters by name, labels, or automatic/manual creation to inspect backup points.

Instructions

List the snapshots of a Storage Box, with optional filtering by name, labels, or automatic-vs-manual.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesStorage Box ID
nameNoFilter by name
sortNoSort field, e.g. "id:asc" or "name:desc"; pass an array for multiple sort fields
is_automaticNoFilter by whether the snapshot was created by the snapshot plan
label_selectorNoLabel filter, e.g. "env=prod,tier=web"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.0.0
    • addedInput schema / properties / sort / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / sort / description
      Previous value: -"Sort field, e.g. \"id:asc\" or \"name:desc\""New value: +"Sort field, e.g. \"id:asc\" or \"name:desc\"; pass an array for multiple sort fields"
    • removedInput schema / properties / sort / type
      Removed value: -"string"
  2. Addedv2.3.1

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds only filter capability (name, labels, automatic-vs-manual) and omits return format, pagination, or authorization needs, so it adds little behavioral context beyond the annotations.

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?

A single, front-loaded sentence with no wasted words. It says what the tool does and the optional filters immediately.

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 simple list tool with full schema coverage and rich annotations, the description is largely sufficient for selection and invocation. It does not cover pagination or differentiate the tool from get_storage_box_snapshot, leaving minor gaps.

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 five parameters including id, name, sort, is_automatic, and label_selector. The description highlights three filter parameters but does not add syntax or semantics beyond the schema, so the baseline of 3 applies.

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 specific verb ('List') and resource ('snapshots of a Storage Box'), making the operation clear. It does not explicitly distinguish itself from sibling get_storage_box_snapshot or mention scope limits, so a 4 rather than 5.

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?

No when-to-use, when-not-to-use, or alternative tools are mentioned. An agent could infer it from the verb, but the description provides no explicit routing guidance versus get_storage_box_snapshot or list_storage_boxes.

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

Deploy Server

Other Tools