Skip to main content
Glama
Sign In
R2 Bucket MCP

R2 Bucket MCP

by ingsamcas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

delete_file

Delete an object from Cloudflare R2 storage by specifying its key. Handles automatic key prefixing when configured.

Instructions

Delete an object from R2 by key (e.g. vitalo/2.1.0/app-release.apk). Global R2_KEY_PREFIX is applied automatically if configured.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "key": "<key>"
    },
    "name": "delete_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYesObject key in the bucket (e.g. vitalo/2.1.0/app-release.apk)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

Discloses that it deletes (destructive) and that a global prefix is applied automatically. Lacks details on error handling (e.g., key not found), idempotency, or authentication requirements. No annotations provided to supplement.

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 sentences, minimal and clear. No wasted words.

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?

Adequate for a simple delete operation with one parameter. Does not specify return value or error cases, but the purpose is clear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers the key parameter with description. The description adds value by explaining the automatic prefix behavior, which is not in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states action (delete) and resource (object from R2). Distinguishes from siblings like get_file, list_files, upload_apk, upload_file. Includes example key and mentions automatic prefix.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implicitly indicates when to use (delete an object). Does not explicitly exclude other scenarios or compare to siblings, but the context of sibling tools provides alternatives.

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