Skip to main content
Glama

list_objects

Retrieve objects from Huawei OBS storage buckets with options for prefix filtering, hierarchical grouping, and paginated results.

Instructions

List objects in a bucket from the 'huawei_obs' source. Supports prefix filtering, delimiter for hierarchical listing, and pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucketYesThe name of the bucket to list objects from
prefixNoFilter objects by key prefix (e.g., 'folder/subfolder/')
delimiterNoCharacter to use for grouping keys (e.g., '/' for folder-like listing)
max_keysNoMaximum number of objects to return (default: 1000)
continuation_tokenNoToken for pagination, returned from previous request

Implementation Reference

  • The handler function for the 'list_objects' tool. It currently returns a placeholder response indicating that implementation is pending, echoing the input arguments.
    async (args) => {
      // TODO: Implement actual object listing with storage provider
      return createToolSuccessResponse({
        message: `Object listing from '${sourceId}' not yet implemented`,
        bucket: args.bucket,
        filter: {
          prefix: args.prefix,
          delimiter: args.delimiter,
          max_keys: args.max_keys,
        },
        source_id: sourceId,
        note: "Storage provider integration pending",
      });
    }
  • Zod schema defining the input parameters for the list_objects tool: bucket (required), prefix, delimiter, max_keys, continuation_token (optional).
    {
      bucket: z.string().describe("The name of the bucket to list objects from"),
      prefix: z.string().optional().describe("Filter objects by key prefix (e.g., 'folder/subfolder/')"),
      delimiter: z.string().optional().describe("Character to use for grouping keys (e.g., '/' for folder-like listing)"),
      max_keys: z.number().optional().describe("Maximum number of objects to return (default: 1000)"),
      continuation_token: z.string().optional().describe("Token for pagination, returned from previous request"),
    },
  • src/server.ts:181-206 (registration)
    Registration of the 'list_objects' tool via server.tool() within the loop for each storage source. The tool name includes a suffix for non-default sources. Includes description, input schema, and handler.
    // list_objects tool
    server.tool(
      `list_objects${toolSuffix}`,
      `List objects in a bucket from the '${sourceId}' source. Supports prefix filtering, delimiter for hierarchical listing, and pagination.`,
      {
        bucket: z.string().describe("The name of the bucket to list objects from"),
        prefix: z.string().optional().describe("Filter objects by key prefix (e.g., 'folder/subfolder/')"),
        delimiter: z.string().optional().describe("Character to use for grouping keys (e.g., '/' for folder-like listing)"),
        max_keys: z.number().optional().describe("Maximum number of objects to return (default: 1000)"),
        continuation_token: z.string().optional().describe("Token for pagination, returned from previous request"),
      },
      async (args) => {
        // TODO: Implement actual object listing with storage provider
        return createToolSuccessResponse({
          message: `Object listing from '${sourceId}' not yet implemented`,
          bucket: args.bucket,
          filter: {
            prefix: args.prefix,
            delimiter: args.delimiter,
            max_keys: args.max_keys,
          },
          source_id: sourceId,
          note: "Storage provider integration pending",
        });
      }
    );
  • TypeScript interface for ListObjectsToolConfig used in configuration, specifying the tool name, source, and optional max_keys.
    export interface ListObjectsToolConfig {
      name: "list_objects";
      source: string;
      /** Maximum objects to list per request */
      max_keys?: number;
    }
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions pagination and filtering capabilities, it doesn't describe important behavioral aspects like rate limits, authentication requirements, error conditions, response format, or whether this is a read-only operation. The description provides basic functional context but misses critical operational details.

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 perfectly concise - a single sentence that efficiently communicates the core functionality and key features. Every word earns its place with zero waste, and it's front-loaded with the primary purpose before mentioning supporting features.

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?

For a 5-parameter tool with no annotations and no output schema, the description provides adequate basic context but leaves significant gaps. It covers what the tool does and key features, but doesn't address behavioral aspects, error handling, or response format. Given the complexity and lack of structured metadata, the description should do more to compensate for these gaps.

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?

With 100% schema description coverage, the input schema already documents all 5 parameters thoroughly. The description adds minimal value by mentioning 'prefix filtering, delimiter for hierarchical listing, and pagination' which aligns with but doesn't significantly expand upon the schema documentation. The baseline score of 3 is appropriate when 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 ('List objects') and resource ('in a bucket from the huawei_obs source'), making the purpose immediately understandable. It distinguishes from siblings like 'list_buckets' by specifying bucket-level listing, though it doesn't explicitly contrast with 'search_objects' or 'get_object'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for listing objects with filtering capabilities, but doesn't explicitly state when to use this tool versus alternatives like 'search_objects' or 'get_object_metadata'. It mentions supported features (prefix, delimiter, pagination) which provides some contextual guidance, but lacks explicit 'when-not-to-use' scenarios or clear alternative recommendations.

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/zq940222/hybrid-mcp'

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