Skip to main content
Glama
akave-ai

Akave MCP Server

by akave-ai

list_objects

Retrieve a list of objects stored in an S3-compatible bucket, with optional prefix filtering to narrow results.

Instructions

List objects in a bucket

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketYesBucket name
prefixNoOptional prefix to filter objects

Implementation Reference

  • Handler function for list_objects tool: calls s3Client.listObjects and formats response as JSON text.
    async ({ bucket, prefix }: ListObjectsParams) => {
      const objects = await this.s3Client.listObjects(bucket, prefix);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              objects.map((obj) => ({
                key: obj.Key,
                size: obj.Size,
                lastModified: obj.LastModified,
              }))
            ),
          },
        ],
      };
    }
  • Zod input schema defining parameters for list_objects tool.
    {
      bucket: z.string().describe("Bucket name"),
      prefix: z
        .string()
        .optional()
        .describe("Optional prefix to filter objects"),
    },
  • TypeScript interface for ListObjectsParams used in handler type annotation.
    interface ListObjectsParams {
      bucket: string;
      prefix?: string;
    }
  • src/server.ts:64-92 (registration)
    Registration of the list_objects tool on the MCP server.
    this.server.tool(
      "list_objects",
      "List objects in a bucket",
      {
        bucket: z.string().describe("Bucket name"),
        prefix: z
          .string()
          .optional()
          .describe("Optional prefix to filter objects"),
      },
      async ({ bucket, prefix }: ListObjectsParams) => {
        const objects = await this.s3Client.listObjects(bucket, prefix);
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(
                objects.map((obj) => ({
                  key: obj.Key,
                  size: obj.Size,
                  lastModified: obj.LastModified,
                }))
              ),
            },
          ],
        };
      }
    );
  • S3Client helper method that performs the actual ListObjectsV2Command to AWS S3-compatible service.
    async listObjects(bucket: string, prefix?: string) {
      const command = new ListObjectsV2Command({
        Bucket: bucket,
        Prefix: prefix,
      });
      const response = await this.client.send(command);
      return response.Contents || [];
    }
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 but doesn't describe key behaviors such as pagination, rate limits, authentication requirements, or what the output looks like (e.g., list format, metadata included). For a read operation with no annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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—a single sentence with no wasted words. It is front-loaded with the core action and resource, making it easy to scan and understand quickly. Every word earns its place by directly stating 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 lack of annotations and output schema, the description is incomplete for a tool with two parameters and no behavioral context. It doesn't explain what the tool returns, how results are formatted, or any operational constraints. For a list operation in a cloud storage context, more details on output and behavior would be helpful.

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 schema description coverage is 100%, with clear descriptions for both parameters ('bucket' and 'prefix'). The description adds no additional meaning beyond what the schema provides, such as examples or constraints. However, since the schema adequately documents the parameters, a baseline score of 3 is appropriate as the description doesn't need to compensate.

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 ('List') and resource ('objects in a bucket'), making the purpose immediately understandable. It distinguishes this from sibling tools like 'list_buckets' or 'list_object_versions' by specifying objects within a bucket. However, it doesn't explicitly mention what type of objects or provide additional context about the listing scope beyond the bucket.

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 when to choose 'list_objects' over 'list_object_versions' or 'list_buckets', nor does it specify prerequisites or contexts for usage. The agent must infer usage from the name and schema 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/akave-ai/akave-mcp'

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