Deletes multiple DNS zone records in one request using zone name and record IDs, enabling bulk DNS cleanup.
Bulk delete DNS zone records [DELETE /v1/dns/zones/{zoneName}/records/bulk] Delete multiple zone records from a DNS Zone
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | JSON request body | |
| zoneName | Yes | Zone name | |
| x-trace-id | No | Identifier to trace group of requests. |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the description adds nothing about safety. For a bulk destructive operation it omits whether the delete is atomic, what happens on partial/invalid record IDs, or whether deletion is recoverable.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the action. The bracketed HTTP path is mildly redundant with the tool name but harmless.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
A destructive, nested-body bulk mutation with no output schema needs more than an endpoint echo: no note on irreversibility, batch limits, or error semantics. Adequate to identify the tool, insufficient to call it confidently.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and both required parameters plus the trace header are documented inline, so the schema carries the burden. The description adds no meaning beyond the schema, which is baseline 3.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('bulk delete DNS zone records') and the 'bulk' qualifier implicitly contrasts with the single-record sibling delete_dns_zone_record. Clear, though it never names the single-record alternative explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied by the word 'bulk' and the endpoint path. There is no explicit guidance on when to choose this over repeated calls to delete_dns_zone_record, nor any prerequisite or limit guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.