Tool
upload_file · Behavior Open worldfile argument automatically. Do not read or pass a local/sandbox path (e.g. /mnt/data/…) and do not construct file.download_url yourself. The bytes are fetched, stored, and processed (text extraction + embeddings) in place. Poll readiness with get_files({ id }) until status is “ready” (then use the file) or “failed” (then extraction_error explains why). Target the upload with project_id (into a project) or scope (“my-files” / “organization”); the two are mutually exclusive and default to “my-files”.
Input parameters
object
required
The file to upload. The host populates this automatically when the user attaches a file. Do not construct it or pass a local/sandbox path (e.g. /mnt/data/…); just call the tool and let the host attach the file reference.
string (uuid)
Upload into a project you can edit. Mutually exclusive with
scope.'my-files' | 'organization'
Upload to the root of “my-files” or “organization”. Mutually exclusive with
project_id. Defaults to “my-files”.Response
string (uuid)
string
number
string
'ready' | 'extracting' | 'embedding' | 'failed'
string
string
string (uuid)
string
string
Plain-language next step: use the file immediately when ready, poll get_files while still processing, or stop on failure.