InfraNest

List DNS zones

list_dns_zones

Read-onlyIdempotent

Your DNS zones, paginated with page and per_page (up to 200), each with its provider, record count, tags and delegation state. Filter with search, credential, tag or status (active, stale, drift for zones whose live DNS disagrees with InfraNest — their nameservers or records —, outside for zones with edits made directly at the DNS provider that nobody has kept or undone yet, or security) and sort with sort (zone, provider, records, synced) and dir; meta.counts holds the totals. Each zone’s outside_changes counts its undecided edits made at the provider. Drift is not an edit at the provider: each zone's outside_changes counts those, and dns_outside_changes lists them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_dns_zones"
  }
}

Input Schema

Name	Required	Description
`tag`	No	Only things with this tag id.
`page`	No	Page number, from 1.
`search`	No	Matches the zone name.
`status`	No	drift: live DNS disagrees with InfraNest (nameservers or records); outside: edits made directly at the DNS provider nobody has kept or undone; security: a DNS security finding.
`per_page`	No	Rows per page, up to 200 (default 25).
`organization_id`	No	The organization to read. Leave it out when the token reaches only one.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026

changedInput schema / properties / status / description

Previous value: -"drift: records differ from the provider; security: a DNS security finding."New value: +"drift: live DNS disagrees with InfraNest (nameservers or records); outside: edits made directly at the DNS provider nobody has kept or undone; security: a DNS security finding."

changedInput schema / properties / status / enum

Previous value: -[
-  "active",
-  "stale",
-  "drift",
-  "security"
-]New value: +[
+  "active",
+  "stale",
+  "drift",
+  "outside",
+  "security"
+]

First observedOct 30, 2026

TDQS

B3.1/5.0

Behavior3/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, and the description adds useful context such as pagination limits, returned zone fields, meta.counts, and status definitions. However, the final sentences about drift and outside_changes are confusing and arguably contradictory, which weakens behavioral clarity.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and is not excessively long, but it repeats outside_changes and includes a muddled drift clarification. It also references unsupported sort and dir parameters, which adds noise rather than useful structure.

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 annotations and no output schema, it does describe returned fields and meta.counts, but it stops short of a complete response shape. The outside_changes/drift explanation is unclear, and the mismatch between described parameters and the actual schema leaves gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents the six actual parameters. The description adds some useful status and pagination meaning, but it also tells the agent to filter by credential and sort with sort and dir, none of which exist in the input schema, creating a risk of invalid calls.

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?

The description gives a specific verb and resource: listing DNS zones. It also names returned fields (provider, record count, tags, delegation state), which makes the tool's scope clear. It does not explicitly name sibling alternatives, but the zone-level scope is distinguishable from list_dns_records and dns_outside_changes.

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?

It explains the available filtering and sorting options and routes one case to a sibling by saying dns_outside_changes lists outside changes. However, it does not explicitly say when to use this tool instead of list_dns_records, dns_zone_changes, or dns_outside_changes, so usage is mostly implied by the filters.

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

All InfraNest tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.