Skip to main content
Glama

s3_put_object

Upload content to an S3 bucket by specifying bucket name, object key, and content data for storage management.

Instructions

Upload an object to an S3 bucket

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketYesThe name of the bucket
keyYesThe key (path) of the object
contentYesThe content to upload

Implementation Reference

  • Handler for the s3_put_object tool. Extracts bucket, key, and content from arguments, creates a PutObjectCommand, sends it to the S3 client, and returns a success message.
    case "s3_put_object": {
      const { bucket, key, content } = request.params.arguments as {
        bucket: string;
        key: string;
        content: string;
      };
      const command = new PutObjectCommand({
        Bucket: bucket,
        Key: key,
        Body: content,
      });
      await s3Client.send(command);
      return {
        content: [
          {
            type: "text",
            text: `Successfully uploaded to ${bucket}/${key}`,
          },
        ],
      };
    }
  • Tool specification including name, description, and input schema for s3_put_object in the ListTools response.
    {
      name: "s3_put_object",
      description: "Upload an object to an S3 bucket",
      inputSchema: {
        type: "object",
        properties: {
          bucket: {
            type: "string",
            description: "The name of the bucket",
          },
          key: {
            type: "string",
            description: "The key (path) of the object",
          },
          content: {
            type: "string",
            description: "The content to upload",
          },
        },
        required: ["bucket", "key", "content"],
      },
    },
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 basic action. It doesn't disclose behavioral traits such as whether this is idempotent, what happens if the key already exists, authentication requirements, rate limits, or error conditions. 'Upload' implies a write operation, but no further context is given.

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 waste. It's front-loaded and efficiently conveys the core purpose without unnecessary details, making it easy to parse quickly.

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 write operation tool with 3 parameters, no annotations, and no output schema, the description is incomplete. It lacks context on behavior, error handling, or return values, which are critical for an agent to use this tool effectively in a real-world scenario.

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?

The input schema has 100% description coverage, so parameters are well-documented there. The description adds no additional meaning beyond the schema, such as explaining parameter interactions or constraints. Baseline 3 is appropriate as 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 ('upload') and target ('object to an S3 bucket'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like s3_read_object or s3_delete_object, which would require mentioning it's specifically for writing/creating objects.

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., bucket must exist), exclusions, or comparisons to siblings like s3_read_object for reading or s3_delete_object for deletion.

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/AM1010101/s3-mcp-server'

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