Skip to main content
Glama
lazyants

hetzner-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List DNS Zones

hetzner_list_zones
Read-onlyIdempotent

List all DNS zones in the Hetzner Cloud project with optional filters by name, mode (primary/secondary), labels, pagination, and sorting.

Instructions

List all DNS zones in the project, with optional filtering by name, mode (primary/secondary), or labels.

Input Schema

NameRequiredDescriptionDefault
modeNoFilter by zone mode
nameNoFilter by name
pageNoPage number
sortNoSort field, e.g. "id:asc" or "name:desc"; pass an array for multiple sort fields
per_pageNoResults per page (max 50)
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. 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, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds only that filtering is optional; it says nothing about pagination (page/per_page exist) or result ordering behavior.

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 zero filler that states the resource and the filtering options in order of importance. Nothing is wasted.

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 whose annotations carry the safety profile and whose schema documents all six parameters, this is largely complete. The absence of any pagination context (despite page/per_page params) is the only meaningful gap.

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 every parameter (mode, name, page, sort, per_page, label_selector) is already documented in the schema. The description restates a subset of the filters but adds no syntax or format detail beyond what the schema provides, so 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 and resource ('List all DNS zones in the project') and enumerates the filter dimensions, making its scope immediately clear. It is distinguishable from single-resource siblings like hetzner_get_zone, though it does not explicitly name them.

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?

The phrase 'with optional filtering by name, mode, or labels' implies when filtering applies, but there is no explicit guidance on when to use this list tool versus hetzner_get_zone or hetzner_list_zone_rrsets. Usage is implied rather than stated.

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