Skip to main content
Glama

Upscale Video

sirv_upscale_video

Upscale a video 2x or 4x with SeedVR or Topaz to raise its resolution while keeping source detail. Studio measures the source video and prices the request from its size and length.

Instructions

Make one video 2 or 4 times larger with SeedVR or Topaz. Give the source size and length in source_width, source_height and source_duration_seconds. Studio measures the source video itself and prices the request from it.

Use it for video only. For an image, use sirv_upscale_image.

Studio also saves the result in the library as a new asset. Returns the video URL. The request can take up to 20 minutes: keep the connection open for that long.

Credits: spends workspace credits. The cost depends on the model and options.

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": {
      "video_url": "<video_url>",
      "source_width": "<source_width>",
      "source_height": "<source_height>",
      "source_duration_seconds": "<source_duration_seconds>"
    },
    "name": "sirv_upscale_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoUpscaler. Default: seedvr-videoseedvr-video
scaleNoHow many times larger: 2 or 4. Default: 2
video_urlYesPublic URL of the video to upscale
source_widthYesWidth of the source video in pixels
source_heightYesHeight of the source video in pixels
source_frame_rateNoFrames per second of the source video, when you know it
target_resolutionNoOutput resolution. Default: autoauto
source_duration_secondsYesLength of the source video in seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.7/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing a real side effect (the result is saved to the library as a new asset), the return value (video URL), a long runtime with a keep-the-connection-open instruction, and that workspace credits are spent with cost varying by model. The only gap is that it doesn't quantify credit cost or describe failure/timeout behavior.

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?

Short, front-loaded paragraphs: purpose first, then the sibling routing, then side effects and timing, then cost. Every sentence carries actionable information with no filler.

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 an 8-parameter, non-idempotent, open-world mutation with no output schema, the description covers the return value, the persistent side effect, the long runtime, and the credit spend. Nothing an agent needs to call it safely is missing.

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 100%, so the baseline is 3, but the description adds genuine meaning: it explains that source_width, source_height and source_duration_seconds are used for pricing and that the studio re-measures the source. It doesn't cover model/scale/target_resolution tradeoffs, which the schema already documents.

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 specific verb and resource ('Make one video 2 or 4 times larger') plus the underlying models (SeedVR or Topaz), and explicitly distinguishes itself from the image sibling. An agent can identify the operation without opening the 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 scopes usage to video and names the alternative for images ('For an image, use sirv_upscale_image'). It also tells the agent which inputs to supply and that the studio measures the source itself, leaving little to inference.

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