AWS MCP Server

Overview Schema Related Servers Score Discussions

s3_object_delete

Delete objects from Amazon S3 buckets by specifying bucket name and object key to remove unnecessary or outdated files from cloud storage.

Instructions

Delete an object from S3

Input Schema

TableJSON Schema

Name	Required	Description	Default
`bucket_name`	Yes	Name of the S3 bucket
`object_key`	Yes	Key/path of the object to delete

Implementation Reference

src/mcp_server_aws/server.py:160-164 (handler)
Executes the S3 object deletion using boto3 s3_client.delete_object with bucket_name and object_key parameters.
```
elif name == "s3_object_delete":
    response = s3_client.delete_object(
        Bucket=arguments["bucket_name"],
        Key=arguments["object_key"]
    )
```

src/mcp_server_aws/tools.py:64-81 (schema)

Defines the Tool object including input schema for s3_object_delete, specifying required bucket_name and object_key.

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"]
    }
),

src/mcp_server_aws/server.py:136-139 (registration)
Registers all AWS tools, including s3_object_delete, by returning 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()
```

Tool Definition Quality

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Delete' which implies a destructive mutation, but doesn't disclose critical behavioral traits like whether deletion is permanent, requires specific IAM permissions, has rate limits, or what happens on success/failure. 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 a single, efficient sentence with zero wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly. Every word earns its place.

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 this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permanence, permissions, error handling, or return values. For a tool that permanently deletes data, more context is needed to use it safely and effectively.

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 both parameters ('bucket_name', 'object_key') clearly documented in the schema. The description adds no additional parameter semantics beyond what the schema provides, 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 action ('Delete') and resource ('an object from S3'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 's3_bucket_delete' or 'dynamodb_item_delete', which would require mentioning it targets individual objects rather than buckets or database items.

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. It doesn't mention prerequisites (e.g., needing appropriate permissions), when not to use it (e.g., for batch deletions), or refer to related tools like 's3_object_list' for finding objects to delete.

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

Install Server

Latest Blog Posts

Tool Definition Quality Score (TDQS)
By punkpeye on April 3, 2026.
mcp
The Hackers Who Tracked My Sleep Cycle
By punkpeye on March 26, 2026.
security
Open Source Has a Bot Problem
By punkpeye on March 19, 2026.
open source

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