Skip to main content
Glama
lazyants

hetzner-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List Image Actions

hetzner_list_image_actions
Read-onlyIdempotent

List all actions performed on a specific image, such as snapshot creation and protection changes. Filter by status and sort results to audit image activity.

Instructions

List all actions performed on a specific image, such as snapshot creation and protection changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesImage ID
pageNoPage number
sortNoSort field, e.g. "id:asc" or "name:desc"; pass an array for multiple sort fields
statusNoFilter by action status: "running", "success", or "error"; pass an array for multiple statuses
per_pageNoResults per page (max 50)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 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"
    • addedInput schema / properties / status / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  }
+]
    • changedInput schema / properties / status / description
      Previous value: -"Filter by action status: comma-separated list of \"running\", \"success\", \"error\""New value: +"Filter by action status: \"running\", \"success\", or \"error\"; pass an array for multiple statuses"
    • removedInput schema / properties / status / type
      Removed value: -"string"
  2. First observedv2.2.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly=true, idempotent=true, and destructive=false, so the safety profile is fully covered. The description adds useful content context (snapshot creation, protection changes) but says nothing about pagination behavior or the shape of a returned action.

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 tight sentence with the verb and resource front-loaded and zero filler. Every clause carries information.

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?

With no output schema, the description carries some burden to characterize returns; it partly does via example action types but omits what an action record contains and any note on pagination. For a 5-param filtered-list tool this is adequate but not complete.

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%, so all five parameters (id, page, sort, status, per_page) are already documented in the schema. The description adds no syntax or format detail beyond that, 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 (actions performed on a specific image) and even names example action types. This clearly distinguishes it from sibling action-list tools like list_server_actions and list_volume_actions by the resource scoped.

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 guidance on when to use this versus related tools such as get_image or other *_actions lists. It implicitly signals 'use to inspect image history' but states no conditions, prerequisites, or alternatives.

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