Skip to main content
Glama

s3_bucket_delete

Delete an S3 bucket by specifying its name to remove storage resources from AWS. This tool helps manage cloud storage by removing unused or unnecessary buckets.

Instructions

Delete an S3 bucket

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucket_nameYesName of the S3 bucket to delete

Implementation Reference

  • Executes the S3 bucket delete operation by calling delete_bucket on the boto3 S3 client with the provided bucket_name.
    elif name == "s3_bucket_delete":
        response = s3_client.delete_bucket(Bucket=arguments["bucket_name"])
  • Defines the schema for the s3_bucket_delete tool, including input validation for the required bucket_name parameter.
    Tool(
        name="s3_bucket_delete",
        description="Delete an S3 bucket",
        inputSchema={
            "type": "object",
            "properties": {
                "bucket_name": {
                    "type": "string",
                    "description": "Name of the S3 bucket to delete"
                }
            },
            "required": ["bucket_name"]
        }
    ),
  • Registers all AWS tools, including s3_bucket_delete, by returning the list from get_aws_tools() in the MCP list_tools handler.
    async def list_tools() -> list[Tool]:
        """List available AWS tools"""
        logger.debug("Handling list_tools request")
        return get_aws_tools()
  • Function that returns the list of S3 tools, including the s3_bucket_delete Tool instance.
    def get_s3_tools() -> list[Tool]:
        return [
            Tool(
                name="s3_bucket_create",
                description="Create a new S3 bucket",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "bucket_name": {
                            "type": "string",
                            "description": "Name of the S3 bucket to create"
                        }
                    },
                    "required": ["bucket_name"]
                }
            ),
            Tool(
                name="s3_bucket_list",
                description="List all S3 buckets",
                inputSchema={
                    "type": "object",
                    "properties": {}
                }
            ),
            Tool(
                name="s3_bucket_delete",
                description="Delete an S3 bucket",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "bucket_name": {
                            "type": "string",
                            "description": "Name of the S3 bucket to delete"
                        }
                    },
                    "required": ["bucket_name"]
                }
            ),
            Tool(
                name="s3_object_upload",
                description="Upload an object to S3",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "bucket_name": {
                            "type": "string",
                            "description": "Name of the S3 bucket"
                        },
                        "object_key": {
                            "type": "string",
                            "description": "Key/path of the object in the bucket"
                        },
                        "file_content": {
                            "type": "string",
                            "description": "Base64 encoded file content for upload"
                        }
                    },
                    "required": ["bucket_name", "object_key", "file_content"]
                }
            ),
            Tool(
                name="s3_object_delete",
                description="Delete an object from S3",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "bucket_name": {
                            "type": "string",
                            "description": "Name of the S3 bucket"
                        },
                        "object_key": {
                            "type": "string",
                            "description": "Key/path of the object to delete"
                        }
                    },
                    "required": ["bucket_name", "object_key"]
                }
            ),
            Tool(
                name="s3_object_list",
                description="List objects in an S3 bucket",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "bucket_name": {
                            "type": "string",
                            "description": "Name of the S3 bucket"
                        }
                    },
                    "required": ["bucket_name"]
                }
            ),
            Tool(
                name="s3_object_read",
                description="Read an object's content from S3",
                inputSchema={
                    "type": "object",
                    "properties": {
                        "bucket_name": {
                            "type": "string",
                            "description": "Name of the S3 bucket"
                        },
                        "object_key": {
                            "type": "string",
                            "description": "Key/path of the object to read"
                        }
                    },
                    "required": ["bucket_name", "object_key"]
                }
            ),
        ]
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Delete an S3 bucket' implies a destructive mutation but doesn't specify critical details: whether this operation is irreversible, what happens to bucket contents, required permissions, error conditions, or rate limits. For a destructive operation with zero annotation coverage, this is a significant gap.

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 extremely concise at just three words, with zero wasted language. It's front-loaded with the core action and resource, making it immediately understandable despite its brevity.

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 deletion tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens to bucket contents, whether deletion is permanent, what permissions are required, or what the response looks like. Given the high-stakes nature of bucket 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%, with the single parameter 'bucket_name' fully documented in the schema. The description doesn't add any parameter semantics beyond what the schema already provides, so it meets the baseline for high schema coverage without adding value.

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 resource ('an S3 bucket'), providing specific verb+resource pairing. However, it doesn't distinguish this tool from sibling tools like 's3_object_delete' or 'dynamodb_table_delete', which reduces its differentiation value.

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 's3_object_delete' or 'dynamodb_table_delete'. There's no mention of prerequisites (e.g., bucket must be empty), consequences, or appropriate contexts for bucket deletion versus other deletion operations.

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/rishikavikondala/mcp-server-aws'

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