Skip to main content
Glama

Kubeez

get_upload_session

Read-onlyIdempotent

Scope: generate:media. PRE-FETCH (mandatory if you haven't already): resources/read kubeez://skills/media-upload AND kubeez://skills/billing-confirmation. The duration fields returned here are what powers exact per-second billing — handle them per the skills.

Fetch uploaded file URLs from a temp upload session created by get_upload_url. Call this after the user confirms they finished uploading at the link (or to poll until files appear). Pass the same token get_upload_url returned. Returns media_urls for use as source_media_urls in generate_media (or other tools expecting HTTPS media URLs). ALSO returns a per-file media array with {url, kind: image|video|audio, duration_seconds?, measurement?, width?, height?, mime_type?, file_size_bytes?} and aggregates total_video_seconds / total_audio_seconds / unknown_duration_count. duration_seconds is the SERVER's own measurement of the file, the exact number length-billed models charge on (e.g. seedance-2-fast-*-video-ref: (ref_video_seconds + output_seconds) × rate; p-video with audio: audio_seconds × rate). Pass it to estimate for an exact quote. billing_readiness is 'exact' only when every audio/video file is measured. If unknown_duration_count > 0, media[].measurement says why ('unavailable': call again shortly; 'unreadable': ask for a standard MP4/MOV/MP3/WAV); length-billed models refuse such a file rather than guess. If count is 0, nothing uploaded yet — remind them to use the link; you cannot substitute local files.

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": {
      "token": "<token>"
    },
    "name": "get_upload_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

Annotations already declare readOnlyHint/idempotent/non-destructive, and the description goes well beyond them: polling semantics, billing consequences of duration_seconds, the meaning of unknown_duration_count, and the fact that length-billed models refuse unmeasured files. Minor deduction because it doesn't state the polling cadence or how long a session stays valid.

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?

Front-loaded with scope and mandatory pre-reads, then the core action, then return semantics. Dense but nearly every sentence carries operational information; the inline rate-formula examples add length that could be compressed without much loss.

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 tool whose outputs drive per-second billing, the description covers the full return shape, aggregation fields, failure modes ('unavailable' vs 'unreadable'), and the correct follow-up action. Even with an output schema present, the behavioral caveats are what an agent needs to act correctly.

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 description coverage is 0% for the single 'token' parameter, so the description must carry it — and it does, specifying that it must be the token returned by get_upload_url. That provenance is exactly the meaning the bare schema lacks.

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?

States a concrete verb and resource: 'Fetch uploaded file URLs from a temp upload session created by get_upload_url.' It also names the downstream consumer (media_urls for generate_media) and the originating sibling, so the agent can place it precisely in the pipeline without opening a schema.

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?

Explicitly says when to call ('after the user confirms they finished uploading... or to poll until files appear'), what to pass ('the same token get_upload_url returned'), and what to do when nothing appears ('remind them to use the link; you cannot substitute local files'). It also names required pre-reads, which is real routing guidance.

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