VideoGen

Get file

get_file

Read-onlyIdempotent

Fetch a file by id with freshly hydrated (non-expired) signed URLs for its thumbnail, preview, and download renditions. Set wait: true to poll until the file finishes processing — use this right after PUTting bytes to a create_file_upload URL.

Input Schema

TableJSON Schema

Name	Required	Description
`wait`	No	When true, poll until the file finishes processing and a rendition is ready. Defaults to false (a single fetch).
`fileId`	Yes	Asset to fetch. Use fileId from upload_file, create_file_upload, list_files, or a generation result.
`timeoutMs`	No	Maximum time to wait for processing before giving up, in milliseconds.
`pollIntervalMs`	No	Time between readiness checks in milliseconds when wait is true. Omit to poll every 3000 milliseconds.

Output Schema

TableJSON Schema

Name	Required	Description
`type`	No	File type once processing has determined it.
`scope`	No	File scope.
`fileId`	Yes	File id (vg_file_...).
`hlsSource`	No
`description`	No	File description when analyzed.
`displayName`	No	Display name for the file.
`downloadUrl`	No	Signed download URL when ready.
`publicHlsUrl`	No
`thumbnailUrl`	No	Signed thumbnail URL when available.
`previewSource`	No
`downloadSource`	No
`sourceToolType`	No
`transcriptText`	No	Plain transcript text when available.
`durationSeconds`	No	Duration in seconds for video/audio; null for images.
`thumbnailSource`	No
`publicPlaybackId`	No
`downloadUrlExpiresAt`	No	Unix expiry for downloadUrl.
`sourceToolExecutionId`	No
`thumbnailUrlExpiresAt`	No	Unix expiry for thumbnailUrl.
`isPublicPreviewEnabled`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 16, 2026

changedInput schema / properties / fileId / description

Previous value: -"File id (vg_file_...)."New value: +"Asset to fetch. Use fileId from upload_file, create_file_upload, list_files, or a generation result."

changedInput schema / properties / pollIntervalMs / description

Previous value: -"How often to poll while waiting, in milliseconds."New value: +"Time between readiness checks in milliseconds when wait is true. Omit to poll every 3000 milliseconds."

First observedOct 9, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds real behavioral context beyond them: URLs are hydrated/non-expired, and wait:true switches the tool into a polling mode until processing finishes — a state-dependent behavior the annotations cannot express.

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 sentences, front-loaded with the core fetch behavior and followed by the conditional polling instruction. No filler, no restatement of the title.

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?

Output schema exists, so return payload details need not be spelled out, and it still names the rendition types an agent will receive. With 100% schema coverage and full annotation coverage, nothing needed to invoke this correctly is missing.

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 description coverage is 100%, so the baseline is 3 and the schema already documents fileId, wait, timeoutMs, and pollIntervalMs. The description still earns credit by tying wait:true to a concrete workflow moment rather than restating the boolean's definition.

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?

States a specific verb (fetch) plus resource (file by id) and further specifies what comes back: freshly hydrated, non-expired signed URLs for thumbnail, preview, and download renditions. That return-oriented detail separates it cleanly from siblings like list_files, upload_file, and create_file_upload.

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

Usage Guidelines4/5

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

Gives an explicit workflow trigger: set wait: true and call this right after PUTting bytes to a create_file_upload URL, naming the sibling it follows. It does not state when NOT to reach for this tool (e.g., versus list_files for discovery), so it stops just short of full routing guidance.

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

All VideoGen tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.