Skip to main content
Glama

Prepare Image Picker Uploads

create_image_picker_uploads

Prepare temporary uploads for the Brand Library image picker opened by open_upload_ui. Supply that Brand's brand_session_id and the selected files' filenames, byte lengths, and MIME types when known. Returns an upload_id and PUT instructions for each file. The picker must upload the bytes and call upload_image to finish saving each image.

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": {
      "brand_session_id": "<brand_session_id>",
      "files": "<files>"
    },
    "name": "create_image_picker_uploads"
  }
}

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.
brand_session_idYesBrand session ID that open_upload_ui opened the picker for.

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.3/5.0
Behavior4/5

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

The annotations already establish that this is a non-read-only, non-destructive, non-idempotent, closed-world operation. The description adds meaningful behavioral context beyond that: uploads are temporary, an upload_id and PUT instructions are returned, and upload_image must be called to finish saving each image. It does not discuss repeated-call implications or rate limits, but it covers the key workflow.

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 description is three efficient sentences with the purpose front-loaded. The second sentence covers required inputs, and the third explains the return value and mandatory follow-up action without redundant wording.

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 staging tool with full schema coverage, an output schema, and annotations, the description is complete enough to invoke correctly. It explains the temporary nature of the uploads and the required upload_image finalization step, which is the critical operational context.

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 brand_session_id, files, filenames, byte_length, content_type, and llm_model are already fully documented in the schema. The description mentions the main inputs and notes MIME types are supplied when known, but adds little semantic detail beyond the structured schema.

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 specific verb and resource: prepare temporary uploads for the Brand Library image picker. It scopes the tool to the picker opened by open_upload_ui and explicitly names upload_image as the finalization step, making it distinguishable from sibling upload tools.

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 clear context for when to use the tool: after open_upload_ui opens the Brand Library image picker. It also explains the required inputs and the next step of uploading bytes and calling upload_image, though it does not explicitly state when not to use it or name an alternative for non-image files.

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