Vidova

Read a cloud export

read_render

Read-onlyIdempotent

Read an owned cloud export's status, actual completed frames, and download URL when successful. A failed export's errorMessage says why and what to do. This does not require an open editor or project. It does not wait: to wait until the render is done, call wait_for_jobs with its job ID. Pass loudness true for a finished render's loudness readout (its loudness field and a text block): momentary LUFS every 0.5 s, integrated LUFS, loudness range and peak, measured from the rendered sound, so a ramp is checked on the file without downloading it. measure_mix reads the same of the timeline before a render.

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": {
      "jobId": "<jobId>",
      "loudness": "<loudness>"
    },
    "name": "read_render"
  }
}

Input Schema

Name	Required	Description	Default
`jobId`	Yes
`loudness`	Yes	true adds the finished render's loudness readout: momentary LUFS every 0.5 s (each the 400 ms before its time), integrated LUFS, loudness range in LU and the loudest sample in dB, measured from the sound as it was mixed for the file, BS.1770 K-weighted as measure_mix measures. null (or leaving it out) leaves it out. A render made before its sound was measured, or a silent one, has none.

Output Schema

Name	Required	Description	Default
`id`	Yes
`notes`	No
`phase`	Yes
`output`	No
`status`	Yes
`endCard`	No
`artifact`	Yes
`attempts`	Yes
`branchId`	Yes
`loudness`	No
`progress`	Yes
`revision`	Yes
`admission`	No
`createdAt`	Yes
`errorCode`	Yes
`projectId`	Yes
`streamUrl`	No
`updatedAt`	Yes
`resolution`	Yes
`totalFrames`	Yes
`errorMessage`	No
`phaseProgress`	Yes
`framesCompleted`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 5, 2026

addedOutput schema / properties / endCard

Added value: +{
+  "properties": {
+    "seconds": {
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "startSeconds": {
+      "minimum": 0,
+      "type": "number"
+    }
+  },
+  "required": [
+    "startSeconds",
+    "seconds"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / notes

Added value: +{
+  "items": {
+    "minLength": 1,
+    "type": "string"
+  },
+  "minItems": 1,
+  "type": "array"
+}

Changed3 schema fields changedOct 27, 2026

changedOutput schema / properties / artifact / anyOf

Previous value: -[
-  {
-    "properties": {
-      "bytes": {
-        "exclusiveMinimum": 0,
-        "maximum": 9007199254740991,
-        "type": "integer"
-      },
-      "downloadUrl": {
-        "format": "uri",
-        "type": "string"
-      },
-      "expiresAt": {
-        "format": "date-time",
-        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$",
-        "type": "string"
-      }
-    },
-    "required": [
-      "bytes",
-      "expiresAt",
-      "downloadUrl"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "bytes": {
+        "exclusiveMinimum": 0,
+        "maximum": 9007199254740991,
+        "type": "integer"
+      },
+      "downloadUrl": {
+        "format": "uri",
+        "type": "string"
+      },
+      "expiresAt": {
+        "format": "date-time",
+        "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$",
+        "type": "string"
+      }
+    },
+    "required": [
+      "bytes",
+      "expiresAt",
+      "downloadUrl"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

changedOutput schema / properties / createdAt / pattern

Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"

changedOutput schema / properties / updatedAt / pattern

Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"

Changed3 schema fields changedOct 24, 2026

addedInput schema / properties / loudness

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "true adds the finished render's loudness readout: momentary LUFS every 0.5 s (each the 400 ms before its time), integrated LUFS, loudness range in LU and the loudest sample in dB, measured from the sound as it was mixed for the file, BS.1770 K-weighted as measure_mix measures. null (or leaving it out) leaves it out. A render made before its sound was measured, or a silent one, has none."
+}

changedInput schema / required

Previous value: -[
-  "jobId"
-]New value: +[
+  "jobId",
+  "loudness"
+]

addedOutput schema / properties / loudness

Added value: +{
+  "properties": {
+    "endSeconds": {
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "integratedLufs": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "momentaryLufs": {
+      "items": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "type": "array"
+    },
+    "peakDb": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "rangeLu": {
+      "anyOf": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "startSeconds": {
+      "minimum": 0,
+      "type": "number"
+    },
+    "stepSeconds": {
+      "const": 0.5,
+      "type": "number"
+    }
+  },
+  "required": [
+    "startSeconds",
+    "endSeconds",
+    "stepSeconds",
+    "momentaryLufs",
+    "integratedLufs",
+    "rangeLu",
+    "peakDb"
+  ],
+  "type": "object"
+}

First observedOct 19, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses that no open editor or project is required, that the call returns immediately rather than polling, and that failures surface an errorMessage explaining cause and remedy. It also explains what the loudness readout contains and the edge cases (silent render, render made before sound was measured) where it is absent.

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?

Front-loaded with the core behavior, then alternatives, then the optional parameter, which is the right order. The loudness sentences are dense and partly duplicate the schema description, so a little trimming would help, but no sentence is filler.

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?

For a read tool with full annotations and an output schema, this covers the state model (success vs failure), timing semantics, and the optional loudness branch well. The one real gap is that it never says how to get a valid jobId in the first place, which matters since it is required.

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 coverage is 50%: the loudness parameter is already heavily documented in the schema, so the description largely restates it, though the comparison to measure_mix adds real meaning. The jobId parameter has no schema description at all, and the text only implies its provenance by pointing at wait_for_jobs rather than saying where to obtain the ID (e.g. list_renders).

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?

Specific verb and resource: reads an owned cloud export's status, completed frame count and download URL. It explicitly scopes to successful exports and contrasts the failure path (errorMessage). It is clearly distinguishable from list_renders, wait_for_jobs and measure_mix, which are named or implied.

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?

States the key exclusion up front: 'It does not wait: to wait until the render is done, call wait_for_jobs with its job ID.' It also names the alternative measurement path (measure_mix reads the timeline before a render) and the condition that selects it, so the agent has both when-to-use and when-to-use-something-else.

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

All Vidova 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.