kinsta_dns_records_deleteDelete a DNS record from your Kinsta-hosted domain by providing domain ID, record type, and name. Resolve unwanted DNS entries in one call.
Delete a DNS record from a domain.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | DNS record name to delete | |
| type | Yes | DNS record type to delete | |
| domain_id | Yes | The domain ID containing the record |
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, so the description doesn't need to repeat that. It adds minimal context beyond the action itself, but doesn't disclose any side effects or irreversibility. With annotations covering the safety profile, a baseline 3 is appropriate.
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?
A single sentence with no filler, front-loads the action and object. Extremely concise.
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?
For a simple delete operation with full parameter documentation and destructive annotation, the description is minimally sufficient. However, it doesn't mention return values or any prerequisites beyond parameters, so a 3 is appropriate.
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 coverage is 100% with descriptions for each parameter, so the schema does the heavy lifting. The description adds no parameter-specific meaning beyond what's in the schema.
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?
The description clearly states the action (Delete) and the resource (DNS record) with a scope (from a domain). It is specific enough to distinguish from create/update siblings, though it doesn't explicitly name alternatives.
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?
No guidance on when to use this tool vs alternatives like kinsta_dns_records_create or update. The description provides no context for selection.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.