Skip to main content
Glama
abushadab

Self-Hosted Supabase MCP Server

by abushadab

list_storage_objects

Retrieve and filter objects from a specific storage bucket in a self-hosted Supabase instance. Specify bucket ID, limit, offset, and prefix for customized results.

Instructions

Lists objects within a specific storage bucket, optionally filtering by prefix.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bucket_idYesThe ID of the bucket to list objects from.
limitNoMax number of objects to return
offsetNoNumber of objects to skip
prefixNoFilter objects by a path prefix (e.g., 'public/')

Implementation Reference

  • The execute handler function that performs the core logic: builds and executes a parameterized SQL query on storage.objects table, applies filters, and returns validated list of objects.
    execute: async (
        input: ListStorageObjectsInput,
        context: ToolContext
    ): Promise<ListStorageObjectsOutput> => {
        const client = context.selfhostedClient;
        const { bucket_id, limit, offset, prefix } = input;
    
        console.error(`Listing objects for bucket ${bucket_id} (Prefix: ${prefix || 'N/A'})...`);
    
        if (!client.isPgAvailable()) {
            context.log('Direct database connection (DATABASE_URL) is required to list storage objects.', 'error');
            throw new Error('Direct database connection (DATABASE_URL) is required to list storage objects.');
        }
    
        // Use a transaction to get access to the pg client for parameterized queries
        const objects = await client.executeTransactionWithPg(async (pgClient: PoolClient) => {
            // Build query with parameters
            let sql = `
                SELECT
                    id,
                    name,
                    bucket_id,
                    owner,
                    version,
                    metadata ->> 'mimetype' AS mimetype,
                    metadata ->> 'size' AS size, -- Extract size from metadata
                    metadata,
                    created_at::text,
                    updated_at::text,
                    last_accessed_at::text
                FROM storage.objects
                WHERE bucket_id = $1
            `;
            const params: (string | number)[] = [bucket_id];
            let paramIndex = 2;
    
            if (prefix) {
                sql += ` AND name LIKE $${paramIndex++}`;
                params.push(`${prefix}%`);
            }
    
            sql += ' ORDER BY name ASC NULLS FIRST';
            sql += ` LIMIT $${paramIndex++}`;
            params.push(limit);
            sql += ` OFFSET $${paramIndex++}`;
            params.push(offset);
            sql += ';';
    
            console.error('Executing parameterized SQL to list storage objects within transaction...');
            const result = await pgClient.query(sql, params); // Raw pg result
    
            // Explicitly pass result.rows, which matches the expected structure
            // of SqlSuccessResponse (unknown[]) for handleSqlResponse.
            return handleSqlResponse(result.rows as SqlSuccessResponse, ListStorageObjectsOutputSchema);
        });
    
        console.error(`Found ${objects.length} objects.`);
        context.log(`Found ${objects.length} objects.`);
        return objects;
    },
  • Zod schemas defining input parameters (bucket_id required, optional limit/offset/prefix) and output structure (array of StorageObject with fields like id, name, metadata). Also includes static MCP JSON input schema.
    // Input schema
    const ListStorageObjectsInputSchema = z.object({
        bucket_id: z.string().describe('The ID of the bucket to list objects from.'),
        limit: z.number().int().positive().optional().default(100).describe('Max number of objects to return'),
        offset: z.number().int().nonnegative().optional().default(0).describe('Number of objects to skip'),
        prefix: z.string().optional().describe('Filter objects by a path prefix (e.g., \'public/\')'),
    });
    type ListStorageObjectsInput = z.infer<typeof ListStorageObjectsInputSchema>;
    
    // Output schema
    const StorageObjectSchema = z.object({
        id: z.string().uuid(),
        name: z.string().nullable(), // Name can be null according to schema
        bucket_id: z.string(),
        owner: z.string().uuid().nullable(),
        version: z.string().nullable(),
        // Get mimetype directly from SQL extraction
        mimetype: z.string().nullable(), 
        // size comes from metadata
        size: z.string().pipe(z.coerce.number().int()).nullable(),
        // Keep raw metadata as well
        metadata: z.record(z.any()).nullable(),
        created_at: z.string().nullable(),
        updated_at: z.string().nullable(),
        last_accessed_at: z.string().nullable(),
    });
    const ListStorageObjectsOutputSchema = z.array(StorageObjectSchema);
    type ListStorageObjectsOutput = z.infer<typeof ListStorageObjectsOutputSchema>;
    
    // Static JSON schema for MCP
    export const mcpInputSchema = {
        type: 'object',
        properties: {
            bucket_id: { type: 'string', description: 'The ID of the bucket to list objects from.' },
            limit: { type: 'number', description: 'Max number of objects to return', default: 100 },
            offset: { type: 'number', description: 'Number of objects to skip', default: 0 },
            prefix: { type: 'string', description: "Filter objects by a path prefix (e.g., 'public/')" },
        },
        required: ['bucket_id'],
    };
  • src/index.ts:119-119 (registration)
    Registration of the list_storage_objects tool into the availableTools object used by the MCP server.
    [listStorageObjectsTool.name]: listStorageObjectsTool as AppTool,
  • src/index.ts:33-33 (registration)
    Import of the listStorageObjectsTool module.
    import listStorageObjectsTool from './tools/list_storage_objects.js';
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 optional filtering but doesn't describe important behavioral aspects like pagination behavior (implied by limit/offset but not explained), authentication requirements, rate limits, error conditions, or what the output looks like. For a tool with 4 parameters and no output schema, 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 perfectly concise at a single sentence that communicates the core functionality. It's front-loaded with the main purpose and includes the optional filtering capability without unnecessary elaboration. Every word serves a purpose, making it efficient for an agent to parse and understand 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 (4 parameters, no output schema, no annotations), the description is insufficiently complete. It doesn't explain what the output contains (object metadata, URLs, sizes), how pagination works with limit/offset, error handling, or authentication requirements. For a storage listing tool that likely returns structured data, the description should provide more context about the expected results and operational constraints.

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 description adds minimal value beyond the input schema, which has 100% coverage. It mentions 'optionally filtering by prefix' which corresponds to the 'prefix' parameter already documented in the schema. The schema already provides clear descriptions for all parameters including bucket_id, limit, offset, and prefix with examples. The description doesn't add any additional context about parameter interactions or usage patterns.

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 ('Lists objects') and resource ('within a specific storage bucket'), making the purpose immediately understandable. It distinguishes from sibling tools like 'list_storage_buckets' by focusing on objects within buckets rather than the buckets themselves. However, it doesn't explicitly contrast with other listing tools like 'list_tables' or 'list_auth_users', which would require more specific differentiation.

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 mentions optional filtering by prefix but doesn't explain when this filtering is appropriate or compare it to other tools for similar tasks. With multiple sibling listing tools available, the lack of contextual guidance leaves the agent to infer usage scenarios independently.

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

Related 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/abushadab/selfhosted-supabase-mcp-basic-auth'

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