NextDNS-Agent-MCP

rewrites

Idempotent

Add or remove custom DNS answers in a NextDNS profile, so a name like nas.home resolves to your own IP or another domain.

Instructions

Add or remove a DNS rewrite on a profile: a domain that answers with your own IP address or another domain, like nas.home for a home server. Use profile(section='rewrites') to see the current ones; use list_entries to block or allow a domain instead. Changes the profile and records it, so undo can put it back; adding one that exists or removing one that doesn't changes nothing, and removing without content removes every rewrite for that name. Returns what was done and the change ID.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	Yes	The domain to answer for, like nas.home or printer.example.com.
`action`	Yes	add or remove.
`content`	No	For add: the IPv4 or IPv6 address, or the domain, to answer with.
`profile`	No	The profile's ID or name. Leave empty for the only profile, or the default one.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 21, 2026

addedInput schema / properties / action / description
```
Added value: +"add or remove."
```

addedInput schema / properties / content / description

Added value: +"For add: the IPv4 or IPv6 address, or the domain, to answer with."

addedInput schema / properties / name / description

Added value: +"The domain to answer for, like nas.home or printer.example.com."

addedInput schema / properties / profile / description

Added value: +"The profile's ID or name. Leave empty for the only profile, or the default one."

First observedv0.8.1Oct 20, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare mutation, idempotency, and non-destructiveness, but the description adds important behavioral detail: changes are recorded and undoable, duplicate adds or missing removes are no-ops, and removing without content deletes every rewrite for that name. It also states what the tool returns, which is useful even though an output schema exists.

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?

The description is dense but front-loaded: it defines the operation, routes to alternatives, explains side effects and edge cases, and states the return, with no wasted sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the mutation semantics, idempotency annotation, full parameter schema, and existing output schema, the description provides everything an agent needs to invoke the tool correctly and understand its side effects.

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

Parameters4/5

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

Schema coverage is 100%, so parameter meanings are already documented. The description still adds value by clarifying that content is the answer value for add, and by explaining the special case where removing without content deletes all rewrites for that name.

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?

States a specific verb and resource: add or remove a DNS rewrite on a profile, with a concrete example of what a rewrite is. It explicitly distinguishes this from viewing rewrites via profile(section='rewrites') and from block/allow behavior via list_entries.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance and names the alternatives: use profile(section='rewrites') to see current rewrites, and use list_entries to block or allow a domain. This directly routes the agent between sibling tools.

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