Skip to main content
Glama
lazyants

hetzner-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List DNS Zone Actions

hetzner_list_zone_actions
Read-onlyIdempotent

Audit DNS zone changes by listing all actions performed, such as imports, TTL changes, and protection toggles. Filter by status or sort.

Instructions

List all actions performed on a specific DNS zone, such as imports, TTL changes, and protection toggles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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)
id_or_nameYesZone ID or name

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful domain context about what kinds of actions appear in the results, but says nothing about pagination behavior or result ordering, so it goes only modestly beyond the structured data.

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?

One sentence, zero filler, with the core verb and resource front-loaded and illustrative examples kept brief. Nothing to trim.

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 read-only list tool with a fully documented schema and no output schema, the description covers what is being listed and the action categories involved. It could note the paginated/filterable nature of results, but no critical invocation detail is missing.

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 (including the id_or_name required field and the status/sort/page/per_page filters) are already documented. The description adds no syntax or filtering detail beyond the schema, which is the expected baseline when the schema does the heavy lifting.

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 DNS zone) and enumerates example action types (imports, TTL changes, protection toggles), which cleanly separates it from hetzner_list_zone_rrsets. It does not explicitly name a sibling or contrast against one, but the resource is unambiguous.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: an agent can infer this audits action history for a zone, but there is no explicit when-to-use, when-not, or routing to alternatives such as hetzner_list_zone_rrsets or hetzner_get_zone. Nothing is misleading, but nothing is spelled out either.

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