Skip to main content
Glama

Get uploaded files

get_file_picker_handoff
Read-onlyIdempotent

Resolve an upload reference from the file picker’s Continue message to the verified files and their workspace. Use the returned upload_id values with tools that accept them in that workspace; use each file's temporary url where a generation model input expects a file URL. The reference itself is not an upload_id. Resolving files does not create or change a brand or add assets to a Brand Library.

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": {
      "reference": "<reference>"
    },
    "name": "get_file_picker_handoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
referenceYesReference sent after the user chooses Continue in the file picker. Resolve it here to obtain the verified upload IDs and their workspace.

Output Schema

NameRequiredDescriptionDefault
filesYesVerified uploaded files.
workspace_idYesWorkspace the files were staged in, or null for a personal workspace that has no ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive, so the bar is lower; the description still adds real context by clarifying that resolution performs no brand creation or change and no asset addition. It does not describe failure behavior for a stale or malformed reference, which would have made it richer.

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 purpose is front-loaded in the first sentence, followed by usage routing, then two short disambiguating negatives. Every sentence carries distinct information; nothing repeats the title or schema.

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

Completeness4/5

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

With annotations and an output schema present, the definition covers purpose, handoff usage, and non-mutation completely enough to call correctly. Only error conditions for an invalid or expired reference are left unstated.

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 the baseline is 3, but the description earns above baseline with the semantic warning that 'the reference itself is not an upload_id' – a distinction the schema does not make. The llm_model analytics parameter is left to the schema, which is acceptable.

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 states a specific verb and resource ('Resolve an upload reference ... to the verified files and their workspace') and explicitly negates brand/library mutation, which separates it from publishing and librarying tools. It stops short of naming the sibling it complements, so an agent must infer the split by behavior rather than by name.

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

Usage Guidelines4/5

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

It gives a clear trigger ('from the file picker's Continue message') and explicit downstream routing: pass upload_id values to tools that accept them, and use the temporary url where a model input expects a file URL. What is missing is explicit exclusion guidance against adjacent tools such as the publish/verify siblings.

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