Skip to main content
Glama
mabeldata

PocketBase MCP Server

by mabeldata

download_file

Retrieve the URL to download a file stored in a specific field of a PocketBase collection record by specifying the collection, record ID, and file field name.

Instructions

Get the URL to download a file from a PocketBase collection record field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionYesThe name or ID of the collection.
fileFieldYesThe name of the file field.
recordIdYesThe ID of the record containing the file.

Implementation Reference

  • Core handler function that validates input, fetches the PocketBase record, extracts the filename from the specified file field, generates the download URL using pb.files.getUrl, and returns it to the client.
    async function downloadFile(args: DownloadFileArgs, pb: PocketBase): Promise<ToolResult> {
        if (!args.collection || !args.recordId || !args.fileField) {
            throw invalidParamsError("Missing required arguments: collection, recordId, fileField");
        }
    
        // Fetch the record to get the filename associated with the file field
        const record = await pb.collection(args.collection).getOne(args.recordId, {
            // Optionally specify fields to fetch only the necessary data
            // fields: `${args.fileField}`
        });
    
        // Ensure the file field exists and has a value
        const fileName = record[args.fileField];
        if (!fileName || typeof fileName !== 'string') {
             throw invalidParamsError(`File field '${args.fileField}' not found or empty on record ${args.recordId}`);
        }
    
        // Get the file URL using the filename from the record
        const fileUrl = pb.files.getUrl(record, fileName); // Use pb.files.getUrl
    
        // Return the URL to the client
        return {
            content: [{ type: 'text', text: `Download URL for ${fileName}: ${fileUrl}` }],
        };
    }
  • ToolInfo registration for 'download_file', including name, description, and JSON schema for input validation.
    {
        name: 'download_file',
        description: 'Get the URL to download a file from a PocketBase collection record field.',
        inputSchema: {
            type: 'object',
            properties: {
                collection: { type: 'string', description: 'The name or ID of the collection.' },
                recordId: { type: 'string', description: 'The ID of the record containing the file.' },
                fileField: { type: 'string', description: 'The name of the file field.' },
                // downloadPath is removed - server cannot directly save files for the client
            },
            required: ['collection', 'recordId', 'fileField']
        }
    }
  • TypeScript interface defining the expected arguments for the download_file tool (note: downloadPath is defined here but not used in implementation).
    export interface DownloadFileArgs {
      collection: string;
      recordId: string;
      fileField: string;
      downloadPath: string;
    }
  • Routing logic in the main handleToolCall function that dispatches 'download_file' calls to the file-tools handler.
    } else if (name === 'upload_file' || name === 'download_file') {
        return handleFileToolCall(name, toolArgs, pb);
  • Inclusion of file tools (including download_file) in the overall tools list returned by registerTools.
    ...listFileTools(),
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 tool returns a URL for downloading, but doesn't mention critical details like whether this requires authentication, if there are rate limits, the URL's validity duration, or error handling for missing files. This leaves significant gaps in understanding the tool's behavior.

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 that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse and understand quickly.

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 moderate complexity (3 parameters, no output schema, no annotations), the description is minimally adequate. It explains what the tool does but lacks details on behavior, usage context, and output handling, which are important for an agent to invoke it correctly without structured support.

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 input schema has 100% description coverage, clearly documenting all three required parameters (collection, fileField, recordId). The description adds no additional semantic context beyond what the schema provides, such as examples or constraints, so it meets the baseline for high schema coverage without compensating value.

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 ('Get the URL to download') and resource ('a file from a PocketBase collection record field'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'upload_file' or 'fetch_record', which would require more specific context about when to use each.

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 like 'fetch_record' (which might retrieve record data including file references) or 'upload_file'. It lacks context about prerequisites, such as needing an existing file in a record, or exclusions, leaving the agent to infer usage from the purpose 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

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/mabeldata/pocketbase-mcp'

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