Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Upscale video

upscale_video

Increase a video's resolution to 2x for final delivery via paid render, returning a served URL. Choose standard precision or FLUX 3 engine for 1080p/2K/4K and optional creative detail enhancement.

Instructions

Upscale a video to higher resolution (2x) for final delivery. Paid render; returns the served URL. A 480p Seedance 2.5 draft: finish_draft (same take, native 1080p). Two engines: the default ('standard') is the safe precision upscaler; engine:'flux' is the FLUX 3 video upscaler (1080p/2K/4K) with an optional mode:'creative' detail-enhancement pass — pick it when the user asks for the FLUX upscaler or wants added detail rather than a faithful enlargement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoFLUX only — 'creative' turns on its detail-enhancement pass; default precise
videoYesthe source video URL
engineNodefault 'standard', the precision upscaler. 'flux' = the FLUX 3 video upscaler

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.256
    • changedInput schema / properties / engine / description
      Previous value: -"default topaz. 'flux' = the FLUX 3 video upscaler"New value: +"default 'standard', the precision upscaler. 'flux' = the FLUX 3 video upscaler"
    • changedInput schema / properties / engine / enum
      Previous value: -[
-  "topaz",
-  "flux"
-]New value: +[
+  "standard",
+  "flux"
+]
  2. Changed2 schema fields changedv0.1.249
    • addedInput schema / properties / engine
      Added value: +{
+  "description": "default topaz. 'flux' = the FLUX 3 video upscaler",
+  "enum": [
+    "topaz",
+    "flux"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / mode
      Added value: +{
+  "description": "FLUX only — 'creative' turns on its detail-enhancement pass; default precise",
+  "enum": [
+    "precise",
+    "creative"
+  ],
+  "type": "string"
+}
  3. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "jobId": {
-      "description": "the render job id — poll get_job with this id to resume or inspect",
-      "type": "string"
-    },
-    "model": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "the product-facing label of the model that rendered it"
-    },
-    "raw": {
-      "description": "the raw job result payload (e.g. images[] for carousel template ads)"
-    },
-    "stillRendering": {
-      "description": "true when the render is still in progress — keep polling get_job with jobId",
-      "type": "boolean"
-    },
-    "url": {
-      "anyOf": [
-        {
-          "type": "string"
-        },
-        {
-          "type": "null"
-        }
-      ],
-      "description": "the served URL of the finished media (absent/null while still rendering)"
-    }
-  },
-  "type": "object"
-}New value: +null
  4. Addedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare this is not read-only, is open-world, not idempotent, and not destructive. The description adds that it is a paid render, returns the served URL, and explains the two engine behaviors, though it does not cover auth or rate-limit details.

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 purpose is front-loaded and most sentences earn their place. The fragment about the 480p Seedance draft is slightly awkward, but the overall description remains appropriately sized for a tool with multiple engines and modes.

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?

For a paid, mutating video-render tool with no output schema, the description covers purpose, payment, return URL, alternatives, and engine/mode behavior. It is largely complete, though async behavior and result expiration are not addressed.

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 schema already documents all three parameters. The description adds meaningful guidance beyond the schema by clarifying that 'standard' is the safe precision upscaler, 'flux' is the FLUX 3 upscaler, and mode:'creative' enables a detail-enhancement pass.

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: upscaling a video to 2x resolution for final delivery. It also distinguishes the default engine from the FLUX engine and points to finish_draft as the alternative for 480p Seedance drafts.

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?

It gives explicit usage conditions: use for final delivery, use finish_draft for a 480p Seedance draft, and choose engine:'flux' when the user asks for the FLUX upscaler or wants added detail rather than a faithful enlargement.

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

Deploy Server

Other Tools