NextDNS-Agent-MCP

create_profile

Create a new NextDNS profile for another device, child, or guest network, optionally copying settings from an existing profile or starting with recommended protections or an empty configuration.

Instructions

Make a new NextDNS profile (for another device, a child, a guest network, ...). This app may change the profiles it makes. copy_from: an existing profile (ID or name) to copy every setting and list from. start (without copy_from): recommended (the usual protections and NextDNS's recommended blocklist) or empty (everything off).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	The new profile's name, like Kids or Guest network.
`start`	No	Without copy_from: recommended (the usual protections and NextDNS's recommended blocklist) or empty (everything off).	recommended
`copy_from`	No	An existing profile (ID or name) to copy every setting and list from.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 21, 2026

addedInput schema / properties / copy_from / description

Added value: +"An existing profile (ID or name) to copy every setting and list from."

addedInput schema / properties / name / description

Added value: +"The new profile's name, like Kids or Guest network."

addedInput schema / properties / start / description

Added value: +"Without copy_from: recommended (the usual protections and NextDNS's recommended blocklist) or empty (everything off)."

First observedv0.8.1Oct 20, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Beyond the functional annotations (which confirm it's a write operation), the description provides a crucial warning: 'This app may change the profiles it makes.' This informs the agent about potential subsequent state modifications or instability.

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 highly concise, front-loading the main purpose and dedicating the subsequent sentences to efficiently explaining the conditional logic of the parameters.

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 that the schema is fully described and an output schema exists, the description has successfully covered the operational complexity—the dependency between the `copy_from` and `start` parameters.

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?

While schema coverage is 100%, the description adds vital semantic meaning by specifying that 'copy_from' accepts either an ID or a name, and by linking the usage of 'start' strictly to the condition that 'copy_from' is absent.

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?

The description uses a specific action verb ('Make') directed at the 'NextDNS profile' resource, clearly stating the tool's function and distinguishing it as a creation action among its numerous profile siblings.

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?

The tool explicitly outlines the two usage modes: either use 'copy_from' to replicate an existing profile, or omit it and use 'start' to set a recommended baseline (recommended/empty). This removes ambiguity for the AI agent.

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