@runapi.ai/veo-3-1-mcp

upscale_video

Increase a video's resolution to 1080p or 4K by creating a Veo 3.1 task on RunAPI, which returns a task ID, status, and output URLs for tracking.

Instructions

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "upscale_video"
  }
}

Input Schema

Name	Required	Description
`wait`	No	Poll until the task reaches a terminal status.
`index`	No	Declared type: integer.
`timeout_ms`	No
`callback_url`	No	Declared type: string.
`source_task_id`	No	Declared type: string.
`poll_interval_ms`	No
`output_resolution`	No	Declared type: string. Known values: "1080p", "4k".

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedv0.2.0Oct 5, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```
- addedInput schema / properties / callback_url / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / index / description
```
Added value: +"Declared type: integer."
```
- changedInput schema / properties / index / type
```
Previous value: -"number"New value: +"integer"
```
- addedInput schema / properties / output_resolution / description
```
Added value: +"Declared type: string. Known values: \"1080p\", \"4k\"."
```
- removedInput schema / properties / output_resolution / enum
```
Removed value: -[
-  "1080p",
-  "4k"
-]
```
- addedInput schema / properties / poll_interval_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / source_task_id / description
```
Added value: +"Declared type: string."
```
- addedInput schema / properties / timeout_ms / maximum
```
Added value: +9007199254740991
```
- addedInput schema / required
```
Added value: +[]
```
Addedv0.1.9Jul 24, 2026
Removedv0.1.7Jul 22, 2026
First observedv0.1.0Jun 24, 2026

TDQS

C2.7/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 discloses that this creates an async task and returns a task id, status, and output URLs, but says nothing about what input video is required (source_task_id appears nowhere in the text), permissions, cost, or how the returned task id relates to get_task. This is thin for a 7-parameter task-creation tool.

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?

Two tight sentences with the operation and return shape front-loaded; nothing is repeated. The parenthetical '(upscale video)' is slightly redundant with the tool name but costs little.

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

Completeness2/5

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

For a 7-parameter, no-annotation, no-output-schema task tool, the description leaves the agent without the critical link between the tool and its input video, and without any behavior beyond 'returns task id, status, output URLs'. It is under-specified relative to the tool's complexity.

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

Parameters2/5

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

Schema coverage is 71% and the description explains none of the 7 parameters — notably source_task_id (which video to upscale), output_resolution, wait, and callback_url. Several schema descriptions are stubs ('Declared type: string'), so the description had room to compensate and does not.

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 gives a specific verb ('Create') and resource ('Veo 3.1 task ... upscale video'), and the upscale intent distinguishes it from siblings like extend_video or text_to_video. The parenthetical buries the actual operation slightly, but the purpose is still recoverable.

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?

There is no when-to-use guidance and no comparison to the obvious alternatives (extend_video, text_to_video, get_task). The agent must infer from the name alone that this is the tool for upscaling rather than extending or generating video.

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

Deploy Server