Skip to main content
Glama
fadlee

PocketBase MCP Server

by fadlee

upload_file_from_url

Upload a file from a URL to attach it to a specific record in a PocketBase collection, enabling remote file integration with database records.

Instructions

Upload a file from URL to a record in PocketBase

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionYesThe name or ID of the collection
fileFieldYesThe name of the file field in the collection schema
fileNameNoOptional custom name for the uploaded file. If not provided, will extract from URL
recordIdYesThe ID of the record to attach the file to
urlYesThe URL to download the file from

Implementation Reference

  • Main execution logic for the upload_file_from_url tool: downloads file from URL using fetch, handles filename extraction and MIME type extension mapping, creates Blob and FormData, uploads to PocketBase record via pb.collection().update().
    export function createUploadFileFromUrlHandler(pb: PocketBase): ToolHandler {
      return async (args: UploadFileFromUrlArgs) => {
        try {
          const { collection, recordId, fileField, url, fileName } = args;
          
          // Download the file from the URL
          const response = await fetch(url);
          if (!response.ok) {
            throw new Error(`Failed to download file from URL: ${response.status} ${response.statusText}`);
          }
          
          // Get the file content as ArrayBuffer
          const arrayBuffer = await response.arrayBuffer();
          
          // Determine the filename
          let finalFileName = fileName;
          if (!finalFileName) {
            // Extract filename from URL
            const urlPath = new URL(url).pathname;
            finalFileName = urlPath.split('/').pop() || 'downloaded-file';
            
            // If no extension, try to get from Content-Type header
            if (!finalFileName.includes('.')) {
              const contentType = response.headers.get('content-type');
              if (contentType) {
                const extension = getExtensionFromMimeType(contentType);
                if (extension) {
                  finalFileName += `.${extension}`;
                }
              }
            }
          }
          
          // Create a Blob from the downloaded content
          const blob = new Blob([arrayBuffer]);
          
          // Create a FormData object and append the file
          const formData = new FormData();
          formData.append(fileField, blob, finalFileName);
          
          // Update the record with the file
          const record = await pb.collection(collection).update(recordId, formData);
          
          return createJsonResponse({
            success: true,
            message: `File '${finalFileName}' uploaded successfully from URL to record ${recordId}`,
            fileName: finalFileName,
            sourceUrl: url,
            record
          });
        } catch (error: unknown) {
          throw handlePocketBaseError("upload file from URL", error);
        }
      };
    }
  • Input schema (zod-like) defining parameters for the tool: collection, recordId, fileField, url (required), fileName (optional).
    export const uploadFileFromUrlSchema = {
      type: 'object',
      properties: {
        collection: {
          type: 'string',
          description: 'The name or ID of the collection'
        },
        recordId: {
          type: 'string',
          description: 'The ID of the record to attach the file to'
        },
        fileField: {
          type: 'string',
          description: 'The name of the file field in the collection schema'
        },
        url: {
          type: 'string',
          description: 'The URL to download the file from'
        },
        fileName: {
          type: 'string',
          description: 'Optional custom name for the uploaded file. If not provided, will extract from URL'
        }
      },
      required: ['collection', 'recordId', 'fileField', 'url']
    } as const;
  • src/server.ts:231-236 (registration)
    Tool registration in the MCP server array, specifying name, description, inputSchema, and handler factory.
    {
      name: "upload_file_from_url",
      description: "Upload a file from URL to a record in PocketBase",
      inputSchema: uploadFileFromUrlSchema,
      handler: createUploadFileFromUrlHandler(pb),
    },
  • TypeScript type interface matching the input schema for type safety.
    export interface UploadFileFromUrlArgs {
      collection: string;
      recordId: string;
      fileField: string;
      url: string;
      fileName?: string;
    }
  • Helper function used by the handler to map MIME types to file extensions when filename lacks extension.
    function getExtensionFromMimeType(mimeType: string): string | null {
      const mimeToExt: Record<string, string> = {
        'image/jpeg': 'jpg',
        'image/png': 'png',
        'image/gif': 'gif',
        'image/webp': 'webp',
        'image/svg+xml': 'svg',
        'text/plain': 'txt',
        'text/html': 'html',
        'text/css': 'css',
        'text/javascript': 'js',
        'application/json': 'json',
        'application/pdf': 'pdf',
        'application/zip': 'zip',
        'application/x-zip-compressed': 'zip',
        'application/msword': 'doc',
        'application/vnd.openxmlformats-officedocument.wordprocessingml.document': 'docx',
        'application/vnd.ms-excel': 'xls',
        'application/vnd.openxmlformats-officedocument.spreadsheetml.sheet': 'xlsx',
        'video/mp4': 'mp4',
        'video/webm': 'webm',
        'audio/mpeg': 'mp3',
        'audio/wav': 'wav'
      };
      
      return mimeToExt[mimeType.toLowerCase()] || null;
    }
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 but only states the basic action. It doesn't mention authentication requirements, rate limits, error conditions, file size limits, supported URL schemes, or what happens if the record doesn't exist. For a mutation tool with zero annotation coverage, this is insufficient.

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's appropriately sized and front-loaded with the core functionality.

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?

For a mutation tool with 5 parameters, no annotations, and no output schema, the description is incomplete. It should address behavioral aspects like authentication needs, error handling, and what the tool returns, given the complexity and lack of structured metadata.

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 all 5 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline for high schema coverage but not providing extra 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 ('Upload a file from URL') and target ('to a record in PocketBase'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from its sibling 'upload_file' (which likely uploads from local storage rather than URL), missing full 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 like 'upload_file' or other file-related tools. It lacks context about prerequisites, appropriate scenarios, or exclusions, leaving the agent without usage direction.

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

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