Skip to main content
Glama

manageSettings

Retrieve or update settings for a NextDNS profile category such as privacy, security, or parental control.

Instructions

Manage a settings category for a NextDNS profile.

Settings categories: - general: Core profile settings (e.g., name, web3 blocking). - privacy: Privacy features such as disguised-tracker blocking and affiliate links. - security: Threat intelligence, Google Safe Browsing, typosquatting protection. - parental: Parental control enablement (safe search, YouTube restricted mode). - performance: ECS, cache boost, and other performance options. - logs: Query-logging enablement and retention. - blockpage: Whether to show a custom block page for blocked queries.

Operations: - get: Retrieve current settings for the category. - update: Apply new settings (requires settings payload).

The settings argument can be a Python dict or a JSON string. For update, first call get to see the current schema, then send only the fields you want to change.

Examples: - get: manageSettings(operation="get", category="privacy", profile_id="abc123") - update: manageSettings(operation="update", category="privacy", profile_id="abc123", settings={"disguisedTrackers": True})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYes
settingsNo
operationYes
profile_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, so description carries full burden. Clearly states operations are get (read) and update (write) with examples. Does not mention idempotency or side effects, but adequately covers expected behavior.

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?

Well-structured with headings for categories and operations. Includes examples. While somewhat lengthy, each sentence adds value and the organization aids readability.

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?

Given no annotations and presence of an output schema, the description covers all essential aspects: purpose, parameters, operation flow, and examples. Sufficient for correct tool invocation.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by detailing each category, explaining the 'settings' argument as dict/JSON string, and providing concrete examples. Adds significant meaning beyond the input 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?

The description specifies 'Manage a settings category for a NextDNS profile' with explicit categories and operations (get/update), clearly distinguishing it from sibling tools like manageProfiles or manageLists.

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

Usage Guidelines4/5

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

Provides clear steps: for update, first call get to see schema, then send only changed fields. Also explains settings argument format. Could be more explicit about when not to use, but context is sufficient.

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/dmeiser/nextdns-mcp'

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