Skip to main content
Glama

s3_list_buckets

List all available S3 buckets in your storage service to manage and access your cloud storage containers.

Instructions

List all S3 buckets

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler implementation for the 's3_list_buckets' tool. Executes ListBucketsCommand via s3Client and returns JSON stringified list of buckets.
    case "s3_list_buckets": {
      const command = new ListBucketsCommand({});
      const response = await s3Client.send(command);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.Buckets || [], null, 2),
          },
        ],
      };
    }
  • src/index.ts:64-70 (registration)
    Tool registration in ListToolsRequestHandler response, defining name, description, and input schema (empty object).
      name: "s3_list_buckets",
      description: "List all S3 buckets",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema definition for 's3_list_buckets' tool: empty object (no parameters required).
    inputSchema: {
      type: "object",
      properties: {},
    },
  • S3Client instance configuration, used by the handler to send ListBucketsCommand.
    const s3Client = new S3Client({
      region: S3_REGION,
      endpoint: S3_ENDPOINT,
      credentials: {
        accessKeyId: S3_ACCESS_KEY_ID,
        secretAccessKey: S3_SECRET_ACCESS_KEY,
      },
    });
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 the action but doesn't disclose behavioral traits like whether this requires specific permissions, how results are formatted (e.g., pagination), rate limits, or error conditions. For a tool 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 waste. It's front-loaded with the core action and resource, making it easy to parse quickly without unnecessary elaboration.

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

Completeness3/5

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

Given the tool's simplicity (0 parameters, no output schema), the description is adequate as a minimum viable explanation. However, without annotations or output schema, it lacks details on behavioral aspects like return format or error handling, leaving clear gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so there's no need for parameter explanation in the description. The baseline for this scenario is 4, as the description appropriately avoids redundant information about non-existent parameters.

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 ('List') and resource ('S3 buckets'), making the purpose immediately understandable. It doesn't distinguish from siblings like s3_list_objects (which lists objects within buckets), but the resource specification is specific enough for basic understanding.

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 s3_list_objects. The description only states what it does, without context about prerequisites, timing, or comparison to 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/AM1010101/s3-mcp-server'

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