Skip to main content
Glama
lazyants

hetzner-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Images

hetzner_list_images
Read-onlyIdempotent

List Hetzner Cloud images including system, snapshot, and backup. Filter by name, type, status, architecture, or labels to find specific images.

Instructions

List all available images, including system, snapshot, and backup images.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFilter by image name
pageNoPage number
sortNoSort field, e.g. "id:asc" or "name:desc"; pass an array for multiple sort fields
typeNoFilter by image type
statusNoFilter by image status
bound_toNoFilter backup images by linked server ID; pass an array for multiple servers
per_pageNoResults per page (max 50)
architectureNoFilter by CPU architecture
label_selectorNoLabel filter, e.g. "env=prod,tier=web"
include_deprecatedNoWhether to include deprecated images

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv3.0.0
    • addedInput schema / properties / bound_to
      Added value: +{
+  "anyOf": [
+    {
+      "description": "Resource ID",
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    {
+      "items": {
+        "description": "Resource ID",
+        "exclusiveMinimum": 0,
+        "maximum": 9007199254740991,
+        "type": "integer"
+      },
+      "type": "array"
+    }
+  ],
+  "description": "Filter backup images by linked server ID; pass an array for multiple servers"
+}
    • addedInput schema / properties / include_deprecated
      Added value: +{
+  "description": "Whether to include deprecated images",
+  "type": "boolean"
+}
    • 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. First observedv2.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds only that multiple image categories are included; it says nothing about pagination defaults, result caps, or filtering behavior beyond the schema.

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?

A single efficient sentence with no filler. Front-loads the operation, though it could be trimmed or extended with marginal cost.

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

Completeness3/5

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

For a read-only list tool with full schema coverage and annotations, the description is minimally sufficient. It does not mention pagination behavior or result shape, but with no output schema and a fully documented parameter set, the gap is minor.

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 description coverage is 100% with per-parameter descriptions and enums for type, status, and architecture, so the schema carries parameter semantics. The description adds no additional meaning about how filters combine or paginate, so the baseline 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?

States a specific verb ('List') and resource ('images') plus the range of image kinds covered (system, snapshot, backup). It is clear what the tool does, though it does not explicitly distinguish itself from the singular sibling hetzner_get_image.

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?

There is no explicit guidance on when to use this versus alternatives such as hetzner_get_image (single image) or hetzner_list_image_actions. The list-vs-get distinction is only implicitly inferable from the name.

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