Skip to main content
Glama

Prepare upload reference

publish_file_picker_handoff

Verify the selected uploads and save them under a short upload reference for the picker’s explicit Continue action. The agent resolves that reference with get_file_picker_handoff to retrieve the exact upload IDs and workspace. Publishing the reference does not create or change a brand or add assets to a Brand Library. Returns the upload reference.

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": {
      "workspace_id": "<workspace_id>",
      "upload_ids": "<upload_ids>"
    },
    "name": "publish_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.
upload_idsYesUpload IDs returned by create_file_picker_uploads.
workspace_idYesDestination selected when opening the file picker. Pass that workspace's ID, or null when the picker targets the personal workspace.

Output Schema

NameRequiredDescriptionDefault
referenceYesUpload reference to resolve with get_file_picker_handoff.

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 readOnlyHint=false, destructiveHint=false and openWorldHint=false, and the description does not contradict them: 'publishing' here writes a reference, not a brand change. It adds real value beyond the annotations by scoping the side effects negatively — no brand creation or mutation, no assets added to a Brand Library — which is exactly the ambiguity the word 'publish' would otherwise create. The one undisclosed trait is the non-idempotent behavior flagged in annotations (what a repeat publish yields, or how long the reference lives).

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?

Four sentences, front-loaded with the action and the reference it produces, followed by the resolution path and the negative side-effect scope. Every sentence carries information, though the brand/Brand Library disclaimer and the 'returns the upload reference' line both lean slightly long for a tool that also has an output 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 an output schema present, the description needn't restate the return shape, and the create-verify-publish-resolve lifecycle is legible from this text plus the named sibling. Remaining gaps are small but real for a stateful, non-idempotent write: lifetime of the reference and duplicate-publish behavior are unstated.

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 upload_ids, workspace_id and llm_model are all documented at the schema level; the description only echoes that upload IDs and workspace are what gets captured. It adds no format, count limit, or null-workspace guidance beyond what the schema already says. Baseline 3 is appropriate when the schema carries the parameter burden.

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 description states a concrete verb and resource: verify the selected uploads and save them under a short upload reference that the picker's Continue action consumes. It explicitly distinguishes itself from the read-side sibling get_file_picker_handoff, so an agent can tell producer from consumer without opening either schema.

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 anchors the call to a precise moment in the workflow — the picker's explicit Continue action — and names get_file_picker_handoff as the follow-up resolution step. It stops short of stating exclusions (e.g. not to call before uploads are verified, or what to do on a second Continue), so it is clear context rather than a full when/when-not rule set.

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