Future Video Studio

Download final video

fvs_download_final_video

Destructive

Download a completed Future Video Studio final render URL to a local file.

Use this only after fvs_get_render_status or fvs_get_paid_render_status returns a final_video_url for a completed render. The tool performs an unauthenticated HTTPS GET to that signed URL and writes the response bytes to output_path on the MCP server's local filesystem. It does not call the FVS Agent API, spend wallet credits, require FVS_AGENT_API_KEY, cancel jobs, or modify remote render state.

Side effects and constraints: output_path is a local filesystem path for the MCP server process, parent directories are created, existing files are not replaced unless overwrite is true, and large videos may take minutes to download. The request timeout is 600 seconds. Use a fresh status check to refresh expired signed URLs, and do not pass arbitrary or untrusted URLs.

Input Schema

TableJSON Schema

Name	Required	Description
`overwrite`	No	Set true only when replacing an existing output_path is intended. Defaults to false to avoid accidental local file overwrites.
`output_path`	Yes	Local filesystem path where the MCP server should write the video, for example C:/Users/me/Videos/fvs-result.mp4 or /tmp/fvs-result.mp4. Parent directories are created. Existing files are refused unless overwrite is true.
`final_video_url`	Yes	HTTPS signed final_video_url returned by a completed fvs_get_render_status or fvs_get_paid_render_status response. Use a fresh status check if the signed URL has expired.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed3 schema fields changedMay 7, 2026

addedInput schema / properties / final_video_url / description

Added value: +"HTTPS signed final_video_url returned by a completed fvs_get_render_status or fvs_get_paid_render_status response. Use a fresh status check if the signed URL has expired."

addedInput schema / properties / output_path / description

Added value: +"Local filesystem path where the MCP server should write the video, for example C:/Users/me/Videos/fvs-result.mp4 or /tmp/fvs-result.mp4. Parent directories are created. Existing files are refused unless overwrite is true."

addedInput schema / properties / overwrite

Added value: +{
+  "default": false,
+  "description": "Set true only when replacing an existing output_path is intended. Defaults to false to avoid accidental local file overwrites.",
+  "title": "Overwrite",
+  "type": "boolean"
+}

First observedMay 6, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Discloses unauthenticated HTTPS GET, local file write, parent directories created, no overwrite unless flag, 600s timeout, URL expiry, and security caution about arbitrary URLs. Complements the destructiveHint annotation by explaining exactly what may be overwritten. No contradiction with annotations.

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?

Structured in three concise sections: operation, usage, and side effects. Every sentence adds context without redundancy, and the length is appropriate for a file-download tool with filesystem side effects.

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?

Covers prerequisites, side effects, timeout, absence of authentication requirements, remote-state non-modification, URL expiration, and local overwrite semantics. With an output schema present, no need to describe return values; the description is sufficient for safe invocation.

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 has 100% coverage with detailed descriptions for all three parameters. The description adds HTTP GET behavior, security warning about untrusted URLs, and file-size/time expectations, going beyond what the schema already provides.

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 specifies verb 'download', resource 'completed Future Video Studio final render URL', and target 'local file'. It clearly separates this from sibling tools that submit, cancel, or retrieve status.

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 instructs to use only after fvs_get_render_status or fvs_get_paid_render_status returns a final_video_url. Also lists exclusions: does not call FVS Agent API, spend credits, cancel jobs, or modify remote state.

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

All Future Video Studio tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.