Skip to main content
Glama

Start an image upload

create_asset_upload

Reserve an upload for one JPEG, PNG or WebP image (max 20 MB) with a role: face, reference, style_ref or brand. Returns a signed uploadUrl valid for 15 minutes: send the raw file bytes there with an HTTP PUT and the returned headers, then call complete_asset_upload. Only use files the user supplied.

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": {
      "filename": "<filename>",
      "contentType": "<contentType>",
      "role": "<role>"
    },
    "name": "create_asset_upload"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
filenameYes
contentTypeYes

Output Schema

NameRequiredDescriptionDefault
methodYes
assetIdYes
headersYes
expiresAtYes
uploadUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the signed uploadUrl, its 15-minute validity, the HTTP PUT requirement with returned headers, and the need to complete the upload afterward. These are substantive operational details an agent needs and that the annotations do not provide.

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 two dense sentences that front-load the core action and constraints, then give the required follow-up sequence. There is no unnecessary 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 three-parameter upload-start tool with an output schema, the description covers the essential behavior: format, size limit, role, the returned upload URL, upload method, and the next required call. Nothing critical to correct invocation is missing.

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 0%, so the description must carry parameter meaning. It adds the 20 MB size cap and notes the accepted image formats, but it mostly repeats enum values from the schema and does not explain what each role (face, reference, style_ref, brand) means.

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: 'Reserve an upload for one JPEG, PNG or WebP image' with an assigned role. It distinguishes this step from the sibling complete_asset_upload by explicitly naming the follow-up call.

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 makes the workflow clear: reserve here, PUT the raw bytes to the returned uploadUrl, then call complete_asset_upload. It also constrains source material ('Only use files the user supplied') but does not compare against alternatives such as import_asset_file.

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