Skip to main content
Glama

openFlow

by io.github.molkex
OverviewDiscussionsAdmin

upscale_video

Upscale an existing generated video (from a prior generate_video call) to a higher resolution -- the same "270p/720p/1080p/4K" choice Flow offers when downloading.

Counts against the weekly free video limit (3 a week without a subscription), like
any other video operation, and spends the account's own Flow credits.

account: the Google account whose project owns media_id. Do not guess it and do not
ask the user: the generate_video result you already have carries it in the
`account_used` field -- pass that value verbatim. A media_id only exists inside the
project of the account that produced it, so any other account returns a clean error.

target_resolution: "1080p", "4K" or "from_360p" (omni_upsampler_360p -- lifts a 360p
draft to normal quality; not yet live-tested). 4K may be locked behind a paid plan tier on some
accounts -- comes back as a clean error rather than a crash, just report it.

Slower than generation: it is kicked off and then polled like a normal video
generation -- returns a job_id to poll with check_job if it is not done within ~40s.

Returns {"media_id": <new upscaled mediaId>, "download_path": "/v1/media/....mp4",
"resolution": ...} when done.

Input Schema

NameRequiredDescriptionDefault
accountYes
media_idYes
target_resolutionNo1080p

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / target_resolution / enum
      Previous value: -[
-  "1080p",
-  "4K"
-]New value: +[
+  "1080p",
+  "4K",
+  "from_360p"
+]
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond annotations, it discloses that the operation counts against the weekly free video limit, spends Flow credits, is slower than generation, may need polling via check_job after ~40 seconds, and returns a job_id when incomplete. It also describes clean errors for wrong-account media_id and locked 4K resolution, which is rich operational context.

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?

The description is long but front-loads the core purpose and then organizes constraints by parameter and operational behavior. Most sentences carry useful information, though a few parenthetical details could be tightened without losing meaning.

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?

With no output schema and 0% schema description coverage, the description still explains inputs, return shape, polling behavior, credit/limit impact, and error conditions. An agent has enough to invoke it correctly and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden and does so well. It explains that account must be the exact account_used value from the prior generate_video result, that media_id is scoped to that account's project, and defines each target_resolution value including the experimental from_360p option and possible 4K plan restrictions.

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: upscale an existing generated video from a prior generate_video call to a higher resolution. It distinguishes this from image upscaling and generation by tying it to generated videos and the same resolution choices Flow offers on download.

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 clearly states the prerequisite context: the video must come from a prior generate_video call, and media_id only exists inside the owning account's project. It also warns not to guess the account and to pass account_used verbatim. However, it does not explicitly compare against sibling video tools like edit_video or extend_video.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All openFlow toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources