PocketBase MCP Server

pb_files_upload

Attach files to specific records in a PocketBase collection by uploading Base64 encoded data, specifying the record ID, field name, and file details for storage.

Instructions

Upload a file to a record field

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "collection": "<collection>",
      "recordId": "<recordId>",
      "fieldName": "<fieldName>",
      "fileData": "<fileData>",
      "fileName": "<fileName>"
    },
    "name": "pb_files_upload"
  }
}

Input Schema

Name	Required	Description
`collection`	Yes	Collection name or ID
`fieldName`	Yes	Field name to store the file in
`fileData`	Yes	Base64 encoded file data
`fileName`	Yes	Original file name
`mimeType`	No	File MIME type
`recordId`	Yes	Record ID to attach the file to

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 22, 2025

TDQS

C2.9/5.0

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 action is an upload, implying a write operation, but doesn't mention permissions required, rate limits, file size constraints, or what happens on success/failure. This leaves significant gaps for a mutation tool.

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, making it easy to understand at a glance.

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 6 parameters, no annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like error handling, return values, or usage constraints, leaving the agent with insufficient context to use it effectively.

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 parameters thoroughly. The description adds no additional meaning beyond implying that 'record field' relates to parameters like collection, recordId, and fieldName, but this is redundant with the schema.

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') and target ('to a record field'), which is specific and unambiguous. However, it doesn't differentiate from sibling tools like pb_files_list_record_files or pb_files_delete, which also deal with files but serve different purposes.

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 pb_files_list_record_files for listing files or pb_records_update for other record modifications. It lacks context about prerequisites, such as needing an existing record or specific permissions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.