Skip to main content
Glama

Video Upscale

video_upscale

Upscales videos to higher resolution using AI models, improving visual quality from a public URL or base64 input.

Instructions

Upscale a video to higher resolution.

Takes a video and upscales it using AI models for enhanced quality. Accepts videos as:

  • Public URLs (recommended, and the ONLY way in for a file of your own - chat clients do not pass files through to tools)

  • Data URIs or raw base64 (for callers that already hold the bytes)

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": "<video>",
      "model": "<model>"
    },
    "name": "video_upscale"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesVideo upscaling model name
scaleNoUpscale factor, only for models with a 'scale' range in the model list (FlashVSR_Tiny: 2-4). Unset, those models use their smallest factor. Models without a range have a fixed factor (e.g. RealESRGAN_Vid_x4) and refuse this field
videoYesVideo as URL, data URI (data:video/mp4;base64,...), or base64 string. URLs are recommended to avoid base64 context bloat.
webhook_urlNoHTTPS URL for deAPI to call when this job finishes. Notifies your own systems; the tool still returns the result here
webhook_secretNo32-255 char key deAPI signs the callback with (HMAC-SHA256). Needs webhook_url. A secret given in chat stays in the transcript

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.3

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the chat-client file-pass-through limitation and the URL-vs-base64 tradeoff, which is real behavioral context beyond the schema. It does not mention credit consumption, whether the job runs asynchronously, or what happens on model/scale mismatch beyond what the schema already says.

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 short paragraphs with a front-loaded purpose sentence and a bulleted input-form list; every line carries information, and the most decision-relevant point (URL is the only viable path for your own file) is emphasized inline.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema covers return values and the schema documents webhook_* and scale thoroughly, so those gaps are acceptable. What remains missing for a 5-param, async, paid generation tool is any mention of the model catalog source, cost implications, or expected turnaround — context an agent would need to call this confidently.

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 meaning the schema lacks: that a user's own file can only arrive as a public URL because chat clients do not forward files. That is a genuine constraint on the `video` parameter rather than a restatement of the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description leads with a specific verb and resource: 'Upscale a video to higher resolution', which an agent can distinguish from image_upscale or the *_price siblings by resource alone. It doesn't explicitly name a sibling or state scope boundaries, but nothing about the purpose is ambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives strong input-selection guidance (URLs recommended, base64 for callers already holding bytes), which implicitly tells the agent how to use it. However, there is no guidance on when to prefer this tool over alternatives, no mention of checking video_upscale_price first, and no note on how model availability relates to get_available_models.

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