Skip to main content
Glama

Create Upload URLs

create_upload_urls

Create 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

NameRequiredDescriptionDefault
filesYesLocal files to stage, described by their filenames, exact byte lengths, and MIME types when known. Their combined size must not exceed 256 MiB.
llm_modelNoThe 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_idNoWorkspace 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

NameRequiredDescriptionDefault
uploadsYesOne upload reservation for each requested file.
message_for_assistantNoContext, 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, it discloses that uploads are private temporary storage, that they expire at `expires_at`, that completed upload_ids remain reusable until expiry, and that reuse does not make consuming operations idempotent (repeating onboarding can create another brand). It also specifies the body must be the raw file, not multipart. Minor gap: it does not describe failure modes for a rejected PUT beyond 'call the consuming tool'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and most sentences carry non-obvious information. However, the workspace-omission rule is stated twice ('omit it for the personal workspace' and later 'Omit this input when staging files in the caller's personal workspace'), and the five-paragraph block is longer than strictly necessary for a single-purpose staging tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a non-obvious multi-step staging tool, the description covers the full lifecycle: request instructions, perform the PUT, pass `upload_id` to a named consuming tool, and confirm completion only when that tool succeeds. With an output schema present, it correctly avoids enumerating return fields while still explaining the key ones (`upload_id`, `url`, `expires_at`, `curl_example`).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: how to source `workspace_id` from `list_brands`/`get_brand`, what omitting it means (personal workspace), how `upload_id` and the temporary `url` are consumed downstream, and that each consuming tool enforces its own file-type and size limits. This exceeds what the schema alone conveys.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a specific verb and resource: 'Create temporary direct-upload instructions for local files.' It immediately clarifies the unusual shape of the operation (instructions, not bytes) and distinguishes it from siblings like `open_upload_ui` and the picker tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states explicit preconditions (client can read local files and make HTTP requests), names the fallback (`open_upload_ui` when MCP Apps is available), and a second fallback (ask for a publicly reachable HTTPS URL). It also states what is not supported (private attachment URLs from the host client), leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources