obambu-cpanel-mcp

remove_dns_record

Remove a DNS record from a zone by specifying its line number. Get the line number from list_dns_records.

Instructions

Remove a DNS record from a zone. line is the record's line number as returned by list_dns_records.

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": {
      "zone": "<zone>",
      "line": "<line>"
    },
    "name": "remove_dns_record"
  }
}

Input Schema

Name	Required	Description	Default
`line`	Yes	Line number of the record to remove
`zone`	Yes	Domain name owning the zone

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jul 31, 2026

TDQS

A4/5.0

Behavior2/5

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

With no annotations provided, the description must fully disclose behavioral traits. It states the operation is 'Remove' but does not mention irreversibility, error handling, or side effects (e.g., propagation delays). The only added context is the origin of `line`, which is useful but insufficient for a destructive operation.

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 a single, concise sentence that front-loads the core purpose and immediately follows with the key parameter clarification. Every word earns its place; no redundancy or fluff.

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?

For a simple tool with two parameters, no output schema, and a clear sibling set (add/edit/list DNS records), the description covers the essential aspects: the operation, the target, and the parameter provenance. It could be richer with a warning about permanence, but overall it is adequate for this level of complexity.

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% with both parameters already described. The description adds meaningful context by explaining that `line` is the line number returned by `list_dns_records`, clarifying its provenance and intended usage beyond the schema's simple type/description.

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 clearly states the action ('Remove') and the target resource ('a DNS record from a zone'), immediately distinguishing it from sibling tools like add_dns_record and edit_dns_record. The verb+resource combination is specific and unambiguous.

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?

It explicitly references `list_dns_records` as the source for the `line` parameter, which implies a prerequisite workflow. However, it does not explicitly state when NOT to use this tool or compare it against edit_dns_record as an alternative, leaving some room for ambiguity.

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

Deploy Server