Skip to main content
Glama
akave-ai

Akave MCP Server

by akave-ai

list_object_versions

Retrieve all versions of objects stored in an S3-compatible bucket, including previous versions when versioning is enabled, to track object history and manage storage.

Instructions

List all versions of objects in a bucket (if versioning enabled)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketYesBucket name
prefixNoPrefix to filter objects

Implementation Reference

  • The MCP tool handler for 'list_object_versions' that invokes the S3 client to list object versions and returns a JSON-formatted response.
    async ({ bucket, prefix }) => {
      const versions = await this.s3Client.listObjectVersions(bucket, prefix);
      return {
        content: [{ type: "text", text: JSON.stringify(versions) }],
      };
    }
  • Zod input schema defining parameters: bucket (required string) and optional prefix (string).
      bucket: z.string().describe("Bucket name"),
      prefix: z.string().optional().describe("Prefix to filter objects"),
    },
  • src/server.ts:295-308 (registration)
    Registration of the 'list_object_versions' tool on the MCP server, including name, description, schema, and inline handler.
    this.server.tool(
      "list_object_versions",
      "List all versions of objects in a bucket (if versioning enabled)",
      {
        bucket: z.string().describe("Bucket name"),
        prefix: z.string().optional().describe("Prefix to filter objects"),
      },
      async ({ bucket, prefix }) => {
        const versions = await this.s3Client.listObjectVersions(bucket, prefix);
        return {
          content: [{ type: "text", text: JSON.stringify(versions) }],
        };
      }
    );
  • S3Client helper method that wraps AWS SDK's ListObjectVersionsCommand to list versions in a bucket with optional prefix.
    async listObjectVersions(bucket: string, prefix?: string) {
      const command = new ListObjectVersionsCommand({
        Bucket: bucket,
        Prefix: prefix,
      });
      return await this.client.send(command);
    }
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 mentions the versioning requirement but fails to describe key traits like pagination, rate limits, error handling, or response format. This leaves significant gaps for a tool that likely returns a list of versions.

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 no wasted words, front-loading the core action and resource. It's appropriately sized for a simple list operation, 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?

Given the tool's complexity (listing versions with potential filtering), lack of annotations, and no output schema, the description is incomplete. It omits details on return values, error cases, and behavioral nuances, failing to compensate for the missing structured data.

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%, so the schema already documents both parameters ('bucket' and 'prefix') adequately. The description doesn't add any meaning beyond what the schema provides, such as explaining how 'prefix' filters versions or the bucket context, meeting the baseline for high coverage.

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 all versions') and resource ('objects in a bucket'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_objects' or 'list_buckets', which would require a more specific distinction to earn a 5.

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 minimal guidance with the conditional 'if versioning enabled', hinting at a prerequisite, but lacks explicit when-to-use advice or alternatives. No mention of when to choose this over 'list_objects' or other siblings, leaving usage unclear.

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