Skip to main content
Glama
hostkey-cloud

hostkey-mcp-server

Official
by hostkey-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

s3_delete_file

Destructive

Permanently delete a specified file from an S3 bucket with explicit confirmation to prevent accidental removal.

Instructions

Delete a file from a bucket (s3/delete_file). DESTRUCTIVE: the file is permanently deleted.

Input Schema

NameRequiredDescriptionDefault
fileYesFile key (name)
s3uidNoS3 account UID; omit only if the token is bound to a single S3 account
bucketYesBucket name
confirmYesMust be true to run the operation.
account_idNoDeprecated alias for s3uid / get_users.id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.8
    • changedInput schema / properties / account_id / description
      Previous value: -"Deprecated alias for s3uid"New value: +"Deprecated alias for s3uid / get_users.id"
  2. Changed2 schema fields changedv1.0.4
    • changedInput schema / properties / account_id / description
      Previous value: -"S3 account ID (if required; check via s3_get_users)"New value: +"Deprecated alias for s3uid"
    • addedInput schema / properties / s3uid
      Added value: +{
+  "description": "S3 account UID; omit only if the token is bound to a single S3 account",
+  "type": [
+    "string",
+    "number"
+  ]
+}
  3. Changed3 schema fields changedv1.0.3
    • changedInput schema / properties / account_id / description
      Previous value: -"ID S3-аккаунта (если требуется; уточняйте через s3_get_users)"New value: +"S3 account ID (if required; check via s3_get_users)"
    • changedInput schema / properties / bucket / description
      Previous value: -"Имя бакета"New value: +"Bucket name"
    • changedInput schema / properties / file / description
      Previous value: -"Ключ (имя) файла"New value: +"File key (name)"
  4. First observedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is known; the description adds only the word 'permanently', which sharpens the consequence but largely restates the annotation. It does not mention the required confirm flag, error behavior for missing files, or idempotency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the effect front-loaded and the destructive warning immediately after. Nothing is wasted.

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

Completeness3/5

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

There is no output schema, and annotations plus schema already cover safety and inputs, so the description is nearly sufficient. However, for an irreversible delete it could state the confirm requirement and what happens on a missing key, which are gaps an agent would want covered.

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 description coverage is 100% and all five parameters (bucket, file, s3uid, confirm, account_id) are documented in the schema, so baseline 3 applies. The description adds no parameter-level meaning such as file-key format or the precedent order between s3uid and the deprecated account_id.

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 and resource ('Delete a file from a bucket') plus the underlying API path, which is clearly distinct from siblings like s3_delete_bucket or s3_get_files. It stops short of naming an alternative tool, so it is clear but not fully differentiated.

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 description gives a strong implicit signal ('DESTRUCTIVE: permanently deleted') that tells the agent this is an irreversible action, but it offers no explicit when-to-use/when-not guidance or routing to sibling tools such as s3_delete_bucket for bucket-level removal.

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