Skip to main content
Glama
runapi-ai

Topaz MCP Server

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

upscale_video

Create a Topaz AI task to upscale a video from a source URL. Returns task ID, status, and output URLs.

Instructions

Create a Topaz task on RunAPI (upscale video). Returns a task id, status, and output URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
waitNoPoll until the task reaches a terminal status.
modelNoRunAPI model slug for this model line.
timeout_msNo
callback_urlNoWebhook URL for terminal Task delivery. Declared type: string.
upscale_factorNoVideo upscale multiplier. Declared type: integer. Known values: 1, 2, 4.
poll_interval_msNo
source_video_urlYesPublic source video URL. Declared type: string.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.2.0
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • changedInput schema / properties / callback_url / description
      Previous value: -"Webhook URL for terminal Task delivery."New value: +"Webhook URL for terminal Task delivery. Declared type: string."
    • removedInput schema / properties / model / enum
      Removed value: -[
-  "topaz-upscale-video"
-]
    • addedInput schema / properties / poll_interval_ms / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / source_video_url / description
      Previous value: -"Public source video URL."New value: +"Public source video URL. Declared type: string."
    • addedInput schema / properties / timeout_ms / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / upscale_factor / description
      Previous value: -"Video upscale multiplier."New value: +"Video upscale multiplier. Declared type: integer. Known values: 1, 2, 4."
    • removedInput schema / properties / upscale_factor / enum
      Removed value: -[
-  1,
-  2,
-  4
-]
    • changedInput schema / properties / upscale_factor / type
      Previous value: -"number"New value: +"integer"
  2. Changed5 schema fields changedv0.1.7
    • addedInput schema / properties / callback_url
      Added value: +{
+  "description": "Webhook URL for terminal Task delivery.",
+  "type": "string"
+}
    • addedInput schema / properties / source_video_url / description
      Added value: +"Public source video URL."
    • addedInput schema / properties / source_video_url / type
      Added value: +"string"
    • addedInput schema / properties / upscale_factor / description
      Added value: +"Video upscale multiplier."
    • addedInput schema / required
      Added value: +[
+  "source_video_url"
+]
  3. First observedv0.1.1

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It notes the tool creates a task and returns id/status/output URLs (useful since there is no output schema), but omits key behavior: that creation is asynchronous, that 'wait' defaults to true and may block/poll, callback/webhook semantics, and any permission or rate-limit constraints.

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 sentences, fully front-loaded with the action and resource, then the return values. No filler or repetition.

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?

For a 7-parameter async task-creation tool with no annotations, the description covers the return shape (compensating for the absent output schema) but leaves behavioral context — async polling, wait default, callbacks, auth — and usage routing incomplete.

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

Parameters3/5

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

Schema description coverage is 71% (missing docs for timeout_ms and poll_interval_ms), so baseline is 3. The description adds no parameter meaning beyond the schema — it never mentions upscale_factor, wait, callback_url, or model semantics.

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?

States a specific verb ('Create') and resource ('Topaz task on RunAPI') with the operation 'upscale video' made explicit, so it is distinguishable from upscale_image. It does not explicitly name or contrast with siblings, but the purpose is unambiguous.

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

Usage Guidelines2/5

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

No guidance on when to use this versus alternatives such as upscale_image (different media type) or get_task (polling an existing task). No prerequisites or conditions are stated; the agent must infer usage entirely.

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