Permanently delete one or more Global Edge CDN edges in Stopped status; set confirm=true to run the destructive operation.
⚠️ Destructive: Permanently delete one or more Global Edge CDN edges. Edges must be in Stopped status. Set confirm=true to execute.
| Name | Required | Description | Default |
|---|---|---|---|
| confirm | No | Must be true to actually execute the destructive operation | |
| edgeIds | Yes | Edge IDs to delete |
Changes observed during successful MCP inspections.
v2.0.1Input schema / properties / edgeIdRemoved value: -{
- "description": "Edge ID to delete",
- "type": "number"
-}Input schema / properties / edgeIdsAdded value: +{
+ "description": "Edge IDs to delete",
+ "items": {
+ "type": "number"
+ },
+ "minItems": 1,
+ "type": "array"
+}Input schema / requiredPrevious value: -[
- "edgeId"
-]New value: +[
+ "edgeIds"
+]v1.10.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and idempotentHint=true. The description adds useful behavioral context beyond those hints: permanence, the stopped-status precondition, and the explicit confirm gate.
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 front-loaded warning sentence with critical constraints and no filler. The warning emoji and colon aid quick scanning.
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 destructive two-parameter mutation with no output schema, the description supplies the essential precondition and confirmation gate. The annotations cover the safety profile, so nothing critical is missing for correct invocation.
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 the schema already documents both confirm and edgeIds. The description repeats the confirm requirement and implies multiple IDs via 'one or more', adding little beyond what the schema provides.
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 the specific verb 'delete' and resource 'Global Edge CDN edges', with scope 'one or more' and permanence. It clearly distinguishes itself from sibling mutation tools like ncloud_edge_stop_edge, ncloud_edge_edit_edge, and ncloud_edge_purge.
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?
Provides a clear prerequisite ('Edges must be in Stopped status') and an execution gate ('Set confirm=true to execute'). It does not explicitly name alternatives or exclusions such as using stop_edge first, so usage context is strong but not exhaustive.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.