NextDNS-Agent-MCP

privacy

Idempotent

Toggle a NextDNS profile's blocklists, native tracking protection, disguised trackers, and affiliate link handling, with validated IDs and undoable changes.

Instructions

Turn a profile's privacy blocklists and native tracking protection on or off, and set its disguised trackers and affiliate links switches. Take the IDs from catalog (kind blocklists or natives); use security for threat protection, parental_control for apps and categories, list_entries for single domains. Changes the profile and records it, so undo can put it back; unknown IDs are refused with close matches, and ones already on or off are skipped. Returns what changed, the change ID and the privacy settings after.

Input Schema

TableJSON Schema

Name	Required	Description
`profile`	No	The profile's ID or name. Leave empty for the only profile, or the default one.
`add_natives`	No	Native tracking protection to turn on, like apple, samsung, windows or xiaomi (from catalog, kind natives).
`add_blocklists`	No	Blocklist IDs to turn on, like oisd or hagezi-pro (from catalog, kind blocklists).
`remove_natives`	No	Native tracking protection to turn off.
`allow_affiliate`	No	true or false: let affiliate and tracking links work. Leave empty to keep it as it is.
`remove_blocklists`	No	Blocklist IDs to turn off.
`disguised_trackers`	No	true or false: block third-party trackers disguised as first-party. Leave empty to keep it as it is.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 21, 2026

addedInput schema / properties / add_blocklists / description

Added value: +"Blocklist IDs to turn on, like oisd or hagezi-pro (from catalog, kind blocklists)."

addedInput schema / properties / add_natives / description

Added value: +"Native tracking protection to turn on, like apple, samsung, windows or xiaomi (from catalog, kind natives)."

addedInput schema / properties / allow_affiliate / description

Added value: +"true or false: let affiliate and tracking links work. Leave empty to keep it as it is."

addedInput schema / properties / disguised_trackers / description

Added value: +"true or false: block third-party trackers disguised as first-party. Leave empty to keep it as it is."

addedInput schema / properties / profile / description

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

addedInput schema / properties / remove_blocklists / description
```
Added value: +"Blocklist IDs to turn off."
```
addedInput schema / properties / remove_natives / description
```
Added value: +"Native tracking protection to turn off."
```

First observedv0.8.1Oct 20, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare the safe/idempotent/non-destructive profile, but the description adds substantive context beyond them: changes are recorded so undo can revert, unknown IDs are refused with close matches, and already-set values are skipped. That is exactly the extra behavior an agent needs for a mutation tool.

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

Conciseness4/5

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

Front-loads purpose, then routing, then behavioral guarantees across three dense sentences with essentially no waste. Slightly packed, but every clause carries information.

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?

For a mutation tool with full annotations, full schema coverage, and an output schema, the description covers purpose, routing, reversibility, and error handling. An agent has everything needed to invoke it correctly; return details are properly left to the output schema.

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 the schema already documents all seven parameters, making 3 the baseline. The description adds a little beyond it by tying IDs to the catalog source and explaining the refusal-with-close-matches behavior for invalid IDs, but it does not add per-parameter syntax detail.

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 (turn on/off, set) plus the exact resources involved (privacy blocklists, native tracking protection, disguised trackers, affiliate links switches). It clearly separates this tool from security, parental_control and list_entries, so an agent can distinguish it from siblings without opening a schema.

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?

Explicitly routes the agent: IDs come from catalog (kind blocklists or natives), while threat protection belongs to security, apps/categories to parental_control, and single domains to list_entries. Nothing about when to pick this vs alternatives is left to inference.

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