Skip to main content
Glama
sjk4425

ncloud-mcp-server

by sjk4425
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ncloud_ncs_delete_objects

DestructiveIdempotent

Delete multiple objects or specific versions from a Ncloud Storage bucket in a single call. Set confirm=true to execute this destructive operation and get per-key results for success or errors.

Instructions

[Ncloud Storage] ⚠️ Destructive: Delete multiple objects (optionally specific versions) from a Ncloud Storage bucket in one call (POST /?delete). Give plain keys or objects with versionId. Returns per-key results (deleted / errors) — the call is HTTP 200 even when some keys fail. Set confirm=true to execute.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keysNoObject keys to delete (current versions). Use `objects` instead to target versions
quietNoQuiet mode — the response lists only failures
confirmNoMust be true to actually execute the destructive operation
objectsNoObjects to delete, each optionally with a versionId
bucketNameYesName of the Ncloud Storage bucket
bypassGovernanceRetentionNoSend x-amz-bypass-governance-retention: true for objects under GOVERNANCE retention

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.15.0
    • changedInput schema / properties / bucketName / description
      Previous value: -"Name of the bucket"New value: +"Name of the Ncloud Storage bucket"
    • addedInput schema / properties / bypassGovernanceRetention
      Added value: +{
+  "default": false,
+  "description": "Send x-amz-bypass-governance-retention: true for objects under GOVERNANCE retention",
+  "type": "boolean"
+}
    • changedInput schema / properties / keys / description
      Previous value: -"Array of object keys to delete"New value: +"Object keys to delete (current versions). Use `objects` instead to target versions"
    • addedInput schema / properties / objects
      Added value: +{
+  "description": "Objects to delete, each optionally with a versionId",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "key": {
+        "description": "Object key",
+        "type": "string"
+      },
+      "versionId": {
+        "description": "Version ID to delete permanently",
+        "type": "string"
+      }
+    },
+    "required": [
+      "key"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / quiet
      Added value: +{
+  "default": false,
+  "description": "Quiet mode — the response lists only failures",
+  "type": "boolean"
+}
    • changedInput schema / required
      Previous value: -[
-  "bucketName",
-  "keys"
-]New value: +[
+  "bucketName"
+]
  2. First observedv1.10.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations (destructiveHint, idempotentHint) already declare the safety profile, and the description adds genuinely useful context: the call returns HTTP 200 even when some keys fail, returns per-key results, and requires confirm=true to execute. This is consistent with the annotations and adds value beyond them.

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?

A single dense paragraph with the destructive warning front-loaded. Each sentence earns its place: purpose, version targeting, return semantics (200-even-on-failure), and the confirm gate. No fluff or repetition.

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

Completeness4/5

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

Given there is no output schema, the description's disclosure of return values (per-key deleted/errors) and the 200-even-on-failure caveat is important and present. It also covers the confirm gate and version targeting. The only minor gap is not pointing to the singular delete alternative, but the description is otherwise complete for a destructive batch operation.

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 covers all 6 parameters at 100% with individual descriptions. The description's 'give plain keys or objects with versionId' largely mirrors what the schema already states for keys/objects, so it adds minimal value beyond the structured fields. Baseline 3 applies.

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?

States a specific verb (Delete), resource (multiple objects from a Ncloud Storage bucket), and scope (batch via POST /?delete, optionally versioned). The 'multiple... in one call' phrasing implicitly distinguishes it from the singular sibling ncloud_ncs_delete_object, though it does not name the alternative explicitly.

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 batch intent ('delete multiple objects... in one call') implies using this when deleting several objects at once, but there is no explicit when-to-use vs. the singular ncloud_ncs_delete_object or the closely related ncloud_delete_multiple_objects, and no exclusions are stated.

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

Deploy Server

Other Tools