Create Upload URLs
create_upload_urlsCreate temporary direct-upload instructions for local files.
Rainbrand's MCP tools do not accept file bytes. Use this tool when the client can
read local files and make HTTP requests. If the client cannot execute the
returned PUT request, use open_upload_ui when MCP Apps is available. Pass
workspace_id to stage files in that workspace, or omit it for the personal
workspace. If neither the picker nor direct upload is usable, ask for a
publicly reachable HTTPS file URL and pass it to the consuming tool. Private
attachment URLs from the host client are not supported.
Uploads belong to one workspace. For an existing brand, use its
workspace_id from list_brands or get_brand: pass the ID when
present, or omit this input when the returned value is null. For a new brand,
select the same workspace here and in onboard_brand. Omit this input
when staging files in the caller's personal workspace.
This tool reserves private temporary storage. It does not create a Library
image, attach brand evidence, install a font, or otherwise finish the user's
task. Each upload body is the raw file, not a multipart form. Run the returned
curl_example after replacing <local-file-path>, then pass upload_id
unchanged to onboard_brand, create_brand_edit as source
evidence, upload_image, or upload_brand_font. Where a generation
model input expects a file URL, pass the upload's temporary url instead.
The task is complete only when that consuming tool returns successfully.
Uploads expire at expires_at. A completed upload_id remains reusable
until expiry. This does not make the consuming operation idempotent—for example,
repeating successful brand onboarding can create another brand. If a PUT
response is unclear, call the consuming tool; it will use completed bytes or
report that they are unavailable. Request new upload instructions after expiry.
Each consuming tool applies its own file-type and size limits.
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": {
"files": "<files>"
},
"name": "create_upload_urls"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| files | Yes | Local files to stage, described by their filenames, exact byte lengths, and MIME types when known. Their combined size must not exceed 256 MiB. | |
| llm_model | No | The model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Omit it or pass "unknown" if you are not certain; the tool runs the same either way. Recorded only for the server developer's analytics. | |
| workspace_id | No | Workspace that will own the temporary uploads. Use the destination workspace's ID from list_workspaces; if its ID is null, omit this input to use the caller's personal workspace. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uploads | Yes | One upload reservation for each requested file. | |
| message_for_assistant | No | Context, explanations, or actionable guidance for the calling assistant. Hosts may display it, but it is not copy that must be shown to the user verbatim. |