Skip to main content
Glama
MCP Dokploy Online
by igoruam

dnsProvider-deleteRecord

Destructive

Deletes a DNS record from a specified zone using its DNS provider and record IDs. Use it to remove obsolete or unwanted records from Dokploy-managed DNS configuration.

Instructions

POST /dnsProvider.deleteRecord

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "dnsProviderId": "<dnsProviderId>",
      "zoneId": "<zoneId>",
      "recordId": "<recordId>"
    },
    "name": "dnsProvider-deleteRecord"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneIdYes
recordIdYes
dnsProviderIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.3/5.0
Behavior1/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the description must add context such as what is irreversibly removed or what permissions are required. Instead it contributes zero behavioral information beyond the route string.

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

Conciseness2/5

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

It is short, but this is under-specification rather than conciseness. The single fragment is a raw endpoint, not a front-loaded statement of purpose an agent can act on.

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

Completeness1/5

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

For a destructive, open-world mutation requiring three undocumented identifiers with no output schema, the definition omits everything an agent needs: what gets deleted, irreversibility, required permissions, and parameter sourcing.

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

Parameters1/5

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

All three parameters (dnsProviderId, zoneId, recordId) have 0% schema description coverage, so the description carries the full burden — but it says nothing about what these identifiers refer to, where to obtain them, or whether the deletion is scoped to a zone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"POST /dnsProvider.deleteRecord" only restates the tool name as an HTTP route. There is no verb-and-resource phrasing beyond what the identifier already conveys, and nothing distinguishes it from siblings such as dnsProvider-remove or dnsProvider-updateRecord.

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

Usage Guidelines1/5

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

No when-to-use guidance, no exclusions, no mention of alternatives. An agent gets no signal about when this is the right call versus dnsProvider-remove or dnsProvider-updateRecord.

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

Deploy Server

Other Tools