Skip to main content
Glama

minio_copy_object

Copy objects between buckets or locations in MinIO storage. Specify source and destination buckets with object names to duplicate files.

Instructions

Copy an object to another location in MinIO

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
source_bucketYesSource bucket name
source_objectYesSource object name
dest_bucketYesDestination bucket name
dest_objectYesDestination object name

Implementation Reference

  • The actual implementation of copy_object method in MinioClient class. Uses MinIO's copy_object API with CopySource to copy objects between buckets/locations.
    def copy_object(
        self,
        source_bucket: str,
        source_object: str,
        dest_bucket: str,
        dest_object: str,
    ) -> dict:
        """Copy an object to another location.
    
        Args:
            source_bucket: Source bucket name
            source_object: Source object name
            dest_bucket: Destination bucket name
            dest_object: Destination object name
    
        Returns:
            Copy result
        """
        from minio.commonconfig import CopySource
    
        result = self._client.copy_object(
            dest_bucket,
            dest_object,
            CopySource(source_bucket, source_object),
        )
    
        return {
            "success": True,
            "source": f"{source_bucket}/{source_object}",
            "destination": f"{dest_bucket}/{dest_object}",
            "etag": result.etag,
            "version_id": result.version_id,
        }
  • Tool registration and input schema definition for minio_copy_object. Defines required parameters: source_bucket, source_object, dest_bucket, dest_object.
    Tool(
        name="minio_copy_object",
        description="Copy an object to another location in MinIO",
        inputSchema={
            "type": "object",
            "properties": {
                "source_bucket": {
                    "type": "string",
                    "description": "Source bucket name",
                },
                "source_object": {
                    "type": "string",
                    "description": "Source object name",
                },
                "dest_bucket": {
                    "type": "string",
                    "description": "Destination bucket name",
                },
                "dest_object": {
                    "type": "string",
                    "description": "Destination object name",
                },
            },
            "required": ["source_bucket", "source_object", "dest_bucket", "dest_object"],
        },
    ),
  • Handler routing in call_tool function that routes minio_copy_object requests to the client.copy_object method.
    elif name == "minio_copy_object":
        result = client.copy_object(
            arguments["source_bucket"],
            arguments["source_object"],
            arguments["dest_bucket"],
            arguments["dest_object"],
        )
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Copy') but doesn't mention whether this requires specific permissions, if it overwrites existing destination objects, what happens on failure, or any rate limits. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence that front-loads the core action ('Copy an object') and specifies the context ('to another location in MinIO') without any wasted words. Every part of the sentence contributes directly to understanding the tool's purpose.

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?

Given the tool's complexity as a mutation operation with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, overwrite behavior, error handling, or return values, which are critical for an agent to use this tool correctly in a MinIO context.

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%, with all parameters clearly documented in the schema (source_bucket, source_object, dest_bucket, dest_object). The description adds no additional parameter semantics beyond implying a copy operation between these locations, so it meets the baseline of 3 where the schema does the heavy lifting.

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 verb ('Copy') and resource ('an object') with the destination context ('to another location in MinIO'), making the purpose immediately understandable. It distinguishes from siblings like 'minio_upload_file' or 'minio_put_object' by focusing on internal copying rather than external uploads, though it doesn't explicitly mention these distinctions.

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?

No guidance is provided on when to use this tool versus alternatives like 'minio_upload_file' for external data or 'minio_put_object' for creating new objects. The description implies usage for internal MinIO object copying but lacks explicit context, prerequisites, or exclusions, leaving the agent to infer based on tool names alone.

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/Raphaelren/minio-mcp'

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