Skip to main content
Glama

Upscale a clip

flow_upscale
Destructive

Upscale generated video clips to 1080p for free or 4K with a direct 50-credit charge, requiring acknowledgment for 4K.

Instructions

Upscale a generated clip. 1080p is FREE on paid plans and should always be taken at download. 4K costs 50 credits, is Ultra-plan only, and is rarely worth it for social content. NOTE: Flow does not show an approval card for upscales, so a 4K upscale bypasses the quote gate — it is charged directly and verified against the balance afterwards.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNo1080p
media_idYesMedia id from flow_list_media
acknowledge_4k_costNoRequired to be true for target=4k, which costs 50 credits unquoted
Behavior5/5

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

Description discloses that 4K upscale bypasses the quote gate, is charged directly, and verified against balance. This adds significant context beyond annotations (destructiveHint=true, readOnlyHint=false). No contradictions.

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?

Two sentences plus a note, all front-loaded and essential. No wasted words.

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?

Covers purpose, usage, behavioral traits, and parameter context. No output schema, so return values not needed. Adequately complete for an agent to select and invoke 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 coverage is 67% (media_id and acknowledge_4k_cost have descriptions; target is enum). Description adds meaning: explains cost and plan requirements for 4K, and that 1080p is free. Complements schema well.

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 title 'Upscale a clip' and description 'Upscale a generated clip' clearly state the tool's action and resource. It distinguishes from sibling tools like flow_generate_video and flow_download by focusing on upscaling.

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?

The description advises using 1080p (free on paid plans, always taken at download) and notes 4K is rarely worth it for social content. It implies when to use but doesn't explicitly state when not to or list alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Sergiorushy326/google-flow-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server