Skip to main content
Glama
pickstar-2002

MinIO Storage MCP

delete_object

Remove specific objects from MinIO storage buckets to manage storage space and maintain organized data structures.

Instructions

删除存储桶中的对象

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketNameYes存储桶名称
objectNameYes对象名称

Implementation Reference

  • Handler for the 'delete_object' tool in the MCP server. Validates input using Zod schema, calls the MinIO client's deleteObject method, and returns a success message.
    case 'delete_object': {
      const { bucketName, objectName } = z.object({
        bucketName: z.string(),
        objectName: z.string()
      }).parse(args);
      
      await this.minioClient.deleteObject(bucketName, objectName);
      return {
        content: [
          {
            type: 'text',
            text: `成功删除对象: ${bucketName}/${objectName}`
          }
        ]
      };
    }
  • JSON input schema for the 'delete_object' tool, defining required bucketName and objectName parameters.
    inputSchema: {
      type: 'object',
      properties: {
        bucketName: { type: 'string', description: '存储桶名称' },
        objectName: { type: 'string', description: '对象名称' }
      },
      required: ['bucketName', 'objectName']
    }
  • src/index.ts:162-173 (registration)
    Registration of the 'delete_object' tool in the list_tools response, including name, description, and schema.
    {
      name: 'delete_object',
      description: '删除存储桶中的对象',
      inputSchema: {
        type: 'object',
        properties: {
          bucketName: { type: 'string', description: '存储桶名称' },
          objectName: { type: 'string', description: '对象名称' }
        },
        required: ['bucketName', 'objectName']
      }
    },
  • Helper method in MinIOStorageClient that ensures connection and calls MinIO client's removeObject to delete the specified object.
    async deleteObject(bucketName: string, objectName: string): Promise<void> {
      this.ensureConnected();
      await this.client!.removeObject(bucketName, objectName);
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose that this is a destructive operation (implied but not explicit), whether it requires specific permissions, what happens on success/failure, or if deletions are permanent/reversible. For a mutation tool with zero annotation coverage, this is inadequate.

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?

The description is a single, clear sentence with zero wasted words. It's front-loaded with the core action and target, making it highly efficient and easy to parse.

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

Completeness2/5

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

For a destructive tool with no annotations and no output schema, the description is insufficient. It doesn't explain what 'delete' entails (permanent removal?), error conditions, return values, or how it differs from 'delete_objects'. Given the complexity and risk of object deletion, more context is needed.

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%, so parameters 'bucketName' and 'objectName' are fully documented in the schema. The description doesn't add any semantic context beyond what the schema provides (e.g., format examples, constraints), meeting the baseline for high schema coverage.

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?

The description '删除存储桶中的对象' clearly states the action (delete) and target (object in a bucket), making the purpose immediately understandable. However, it doesn't differentiate from sibling 'delete_objects' (plural), which suggests this tool handles single-object deletion versus batch deletion.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'delete_objects' or 'delete_bucket'. There's no mention of prerequisites (e.g., bucket must exist), exclusions, or comparative context with sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pickstar-2002/minio-storage-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server