Skip to main content
Glama
Venice MCP Server

Venice MCP Server

Official
by veniceai

Venice Video Retrieve / Status

venice_video_status
DestructiveIdempotent

Check a queued video job's status to return JSON progress or the completed video resource when processing finishes.

Instructions

Check status of a queued video job. Returns JSON progress while PROCESSING. Completed jobs are either an embedded base64 video/mp4 MCP resource or a download_url resource link. For VPS / Grok Imagine Private models, retrieve returns COMPLETED JSON without a URL: this process reuses the queue-time download_url when venice_video_generate ran here, or accepts a Venice-host download_url argument. POST endpoint with body {model, queue_id}. Supports x402 wallet auth (no Venice account needed) and API key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "queue_id": "<queue_id>",
      "model": "<model>"
    },
    "name": "venice_video_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesSame model id used to queue.
queue_idYesReturned by venice_video_generate.
download_urlNoQueue-time download_url from venice_video_generate. Must be an https Venice host. Needed for VPS / Grok Imagine Private only when this process did not queue the job (retrieve returns COMPLETED without a URL).
delete_media_on_completionNoDelete server-side media after an embedded MP4 has been buffered, before the tool result returns to the client. Ignored for download_url results: download first, then call venice_video_complete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • changedInput schema / properties / delete_media_on_completion / description
      Previous value: -"Delete server-side media once an embedded MP4 has been buffered. Ignored for download_url results: download first, then call venice_video_complete."New value: +"Delete server-side media after an embedded MP4 has been buffered, before the tool result returns to the client. Ignored for download_url results: download first, then call venice_video_complete."
  2. Changed2 schema fields changedv0.3.0
    • addedInput schema / properties / delete_media_on_completion / description
      Added value: +"Delete server-side media once an embedded MP4 has been buffered. Ignored for download_url results: download first, then call venice_video_complete."
    • addedInput schema / properties / download_url
      Added value: +{
      +  "description": "Queue-time download_url from venice_video_generate. Must be an https Venice host. Needed for VPS / Grok Imagine Private only when this process did not queue the job (retrieve returns COMPLETED without a URL).",
      +  "format": "uri",
      +  "type": "string"
      +}
  3. First observedv0.2.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description explains why destruction occurs: delete_media_on_completion removes server-side media once the MP4 is buffered. It also discloses auth modes (x402 wallet or API key) and the POST body shape, which annotations cannot convey. It doesn't cover failure/expiry behavior for a queue_id, so not a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, which is good, but the VPS / Grok Imagine Private sentence is dense and duplicates schema text about the retrieve endpoint returning COMPLETED without a URL. The prose is jargon-heavy ('this process reuses the queue-time download_url') and would benefit from trimming or bullets.

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?

With no output schema, the description carries the return-value burden and does describe the three result shapes (progress JSON, base64 resource, download_url link). Combined with the destructive-parameter explanation and auth notes, an agent has enough to call it correctly. Missing only operational detail such as what a pending/expired queue_id looks like.

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 coverage is 100%, so all four parameters are already fully documented, establishing a baseline of 3. The description adds limited extra meaning, mainly restating that the body is {model, queue_id} and reiterating the VPS download_url fallback already spelled out in the schema. No new format, default, or constraint information beyond the schema.

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?

Opens with a specific verb+resource ('Check status of a queued video job') and immediately characterizes the two possible completed outcomes (embedded base64 resource vs download_url link). It is clearly distinguishable from venice_video_generate (queueing) and venice_video_complete (post-download cleanup), though those siblings are only referenced indirectly rather than named as alternatives.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent infers this is a polling step after venice_video_generate. The only explicit routing is 'download first, then call venice_video_complete' for download_url results, which is narrow. There is no guidance on polling cadence, when to stop, or when to prefer another tool.

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