OVHcloud MCP Server

ovh_domain_dns_delete

Delete a DNS record from a specified zone by providing the record ID. Use with caution as this action is irreversible.

Instructions

Delete a DNS record (careful!)

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>",
      "recordId": "<recordId>"
    },
    "name": "ovh_domain_dns_delete"
  }
}

Input Schema

Name	Required	Description	Default
`zone`	Yes	DNS zone (domain name, e.g. example.com)
`recordId`	Yes	DNS record ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.1Jun 8, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only implies destructiveness with '(careful!)' but does not detail effects like irreversibility, required permissions, or impact on zone functionality. More context (e.g., 'This action is irreversible') is needed.

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?

The description is very concise with one sentence and a parenthetical warning. Every word serves a purpose. It could be slightly more structured (e.g., separating the warning), but overall it is efficient.

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?

Given the tool's destructive nature (delete) and absence of annotations and output schema, the description is incomplete. It fails to mention that the action is permanent, what happens to related data, or any confirmation step. More behavioral context is required for safe usage.

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 coverage is 100% with parameter descriptions already explaining 'zone' and 'recordId'. The description adds no extra semantic meaning beyond the schema, so a baseline score of 3 is appropriate.

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 ('Delete') and resource ('a DNS record'), making the tool's purpose immediately obvious. The warning '(careful!)' adds caution. Among sibling tools, 'delete' is distinct from create, update, and list operations.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, or prerequisites (e.g., needing the DNS zone and record ID). The warning '(careful!)' hints at caution but does not explain when deletion is appropriate or what checks to perform first.

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