Skip to main content
Glama
lazyants
by lazyants

List DNS Zones

hetzner_list_zones
Read-onlyIdempotent

Retrieve a list of all DNS zones in your Hetzner project, with filters for name, mode (primary/secondary), and labels.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoFilter by name
modeNoFilter by zone mode
label_selectorNoLabel filter, e.g. "env=prod,tier=web"
sortNoSort field, e.g. "id:asc" or "name:desc"
pageNoPage number
per_pageNoResults per page (max 50)
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description confirms read-only nature but adds nothing beyond what annotations provide.

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?

Single sentence, no wasted words, front-loaded with action and resource.

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?

Adequate for a read-only list tool with well-documented schema and annotations. Missing output schema but not critical for a list operation.

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 description adds marginal value. Mentions name, mode, and label filters but does not elaborate beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states verb 'list' and resource 'DNS zones', includes filtering options. Distinguishes from sibling list tools by targeting zones specifically.

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?

Implies usage for listing zones with filters, but no explicit guidance on when to use this tool versus alternatives like hetzner_get_zone or other list tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lazyants/hetzner-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server