Vidova

List cloud exports

list_renders

Read-onlyIdempotent

List this account's cloud exports, newest first, with when each was made (createdAt), its project and its film revision: every project's, or one project's with projectId. Use next as before to fetch the next page; null begins at the newest job.

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": {
      "before": "<before>",
      "limit": "<limit>",
      "projectId": "<projectId>"
    },
    "name": "list_renders"
  }
}

Input Schema

Name	Required	Description
`limit`	Yes
`before`	Yes
`projectId`	Yes	One project's exports only, or null (or leaving it out) for every project's.

Output Schema

Name	Required	Description	Default
`jobs`	Yes
`next`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 6, 2026

addedInput schema / properties / projectId

Added value: +{
+  "anyOf": [
+    {
+      "pattern": "^[A-Za-z0-9_-]{1,128}$",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "One project's exports only, or null (or leaving it out) for every project's."
+}

changedInput schema / required

Previous value: -[
-  "before",
-  "limit"
-]New value: +[
+  "before",
+  "limit",
+  "projectId"
+]

Changed2 schema fields changedNov 5, 2026

addedOutput schema / properties / jobs / items / properties / endCard

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

addedOutput schema / properties / jobs / items / properties / notes

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

Changed3 schema fields changedOct 27, 2026

changedOutput schema / properties / jobs / items / 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 / jobs / items / 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 / jobs / items / 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))$"

Changed1 schema field changedOct 24, 2026

addedOutput schema / properties / jobs / items / 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

A3.7/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description still adds useful behavior: result ordering, that null starts at the newest job, and how continuation works. It does not mention page-size limits or what happens with an invalid/stale cursor, which keeps it below 5.

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 sentences, front-loaded with the resource and ordering, with no filler. The phrase 'Use next as before' is slightly compressed to the point of ambiguity, and the trailing 'null begins at the newest job' clause would read better attached to before directly.

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?

An output schema exists, so return-field enumeration need not be explained, and the description covers ordering, scoping, and pagination -- the three things an agent needs to page correctly. The unexplained required limit parameter is the main remaining hole for a 3-parameter filtered list tool.

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 only 33%, so the description must compensate. It does explain projectId semantics (though that largely repeats the schema's own description) and clarifies that before accepts null to start at the newest job and otherwise takes the previous response's next. The limit parameter, which is required, is never mentioned, leaving a meaningful gap.

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 and resource ('List this account's cloud exports') plus ordering ('newest first') and the fields returned (createdAt, project, film revision), so it is clearly distinguishable from nearby tools like read_render or list_projects. It stops short of explicitly naming the sibling it is not, which keeps it from a 5.

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?

It gives a real scoping rule -- fetch every project's exports, or one project's by supplying projectId -- and explains pagination continuation via the response's next value. There is no explicit statement of when to choose this tool over read_render or other render-related siblings, so the routing guidance is implied rather than stated.

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.