obambu-cpanel-mcp

edit_dns_record

Edit an existing DNS record by specifying its line number from list_dns_records, updating the record type, TTL, and value fields.

Instructions

Edit an existing DNS record. 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>",
      "type": "<type>"
    },
    "name": "edit_dns_record"
  }
}

Input Schema

Name	Required	Description
`ttl`	No
`line`	Yes	Line number of the record in the zone (from list_dns_records)
`type`	Yes	Record type: A, AAAA, CNAME, MX, TXT, NS, SRV, CAA...
`zone`	Yes	Domain name owning the zone
`fields`	No	Type-specific value fields to update for this record type

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jul 31, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states 'Edit an existing DNS record' without mentioning side effects, whether updates are partial or full, error behavior, or permission requirements. This is a significant gap 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.

Conciseness5/5

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

The description is extremely concise, consisting of one main sentence plus a brief clarification of the `line` parameter. Every word earns its place, and the most important usage hint is front-loaded.

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

Completeness2/5

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

Despite having 5 parameters, a nested `fields` object, and no output schema, the description provides only minimal context. It does not explain how `fields` is structured, what TTL means, or the behavior of the edit operation. The helpful line-number hint is not enough to make this complete for a mutation tool with complex inputs.

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

Parameters3/5

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

Schema description coverage is 80%, so baseline is 3. The description repeats the schema's explanation of `line` but does not add further meaning to other parameters. TTL has no schema description and is not covered in the tool description. Overall, the description adds no extra semantic value beyond the schema.

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

Purpose4/5

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

The description clearly states the tool edits an existing DNS record, using the specific verb 'Edit' and resource 'DNS record'. It is distinguishable from sibling tools like add_dns_record and remove_dns_record, though it does not explicitly name them as alternatives.

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

Usage Guidelines3/5

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

The description implies when to use the tool (to edit an existing record) and provides a critical prerequisite by noting that `line` is the record line number from list_dns_records. However, it does not explicitly discuss when not to use it or how it compares to add/remove operations.

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

Deploy Server