Skip to main content
Glama
Sign In

Vidova

by ai.vidova
OverviewDiscussionsAdmin

Wait for jobs

wait_for_jobs
Read-onlyIdempotent

Wait for jobs you started, all in one call. A generation (generate_image, generate_video, generate_speech, generate_music, copy_motion, replace_person, edit_video, lip_sync) answers at once with a Job ID and runs in the background; a long tool (tracking, a cutout, an analysis, an import) answers with a Job ID when it runs longer than one call; render_video answers with its render's id, which works here too. Pass every Job ID you are waiting for. It returns when all of them have finished or after timeoutSeconds, whichever comes first, with each job's own result: an Asset ID to place, a render's status and download link (as read_render gives them), or why it failed. A generation's Asset ID comes once it is placeable (its file encoded, its size and length known), with its source facts, what fit="cover" does to it in the film, a READY line and the use line: patch_film can place it at once. untilPlaceable false answers when the generation ends instead, and an output not placeable yet says NOT PLACEABLE YET with the wait_for_asset call that waits for it. A job still running is listed with its Job ID, its progress (percent done, time left and queue position when its record holds them, else unknown) and when to look again: call wait_for_jobs again with the ones still running. Never start a job again to get its result. projectId is the project the jobs were started in: null (or leaving it out) uses the open project.

Input Schema

NameRequiredDescriptionDefault
jobIdsYesThe Job IDs to wait for, 1 to 20.
projectIdYesThe project this call runs on without changing the open project. null (or leaving it out) uses the open project. wait_for_jobs takes the projectId of the calls that started the jobs.
timeoutSecondsYesHow long to wait at most, 1 to 50. Normally 50: it returns as soon as every job is done.
untilPlaceableYesnull or true: a generation is answered once its output is placeable (encoded, size and length known), so patch_film can place it at once. false: answered when the generation ends, maybe before its output is placeable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / timeoutSeconds / description
      Previous value: -"How long to wait at most, 1 to 300. Normally 300: it returns as soon as every job is done."New value: +"How long to wait at most, 1 to 50. Normally 50: it returns as soon as every job is done."
    • changedInput schema / properties / timeoutSeconds / maximum
      Previous value: -300New value: +50
  2. Changed2 schema fields changed
    • addedInput schema / properties / untilPlaceable
      Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "null or true: a generation is answered once its output is placeable (encoded, size and length known), so patch_film can place it at once. false: answered when the generation ends, maybe before its output is placeable."
+}
    • changedInput schema / required
      Previous value: -[
-  "jobIds",
-  "timeoutSeconds",
-  "projectId"
-]New value: +[
+  "jobIds",
+  "timeoutSeconds",
+  "untilPlaceable",
+  "projectId"
+]
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description explains blocking behavior, timeout semantics, partial results, progress reporting, placeability rules, and the READY/use-line output behavior. It adds substantial operational context without contradicting the annotations.

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?

The description is front-loaded with the core purpose and is generally efficient for a complex waiting tool. However, it is a dense single paragraph with several nested clauses, so it is slightly harder to scan than it could be.

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?

Given the tool's complexity, absence of an output schema, and the need to explain asynchronous job behavior, the description is complete. It covers return values, progress reporting, failure reasons, placeability, and follow-up actions.

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 the schema already documents all four parameters thoroughly. The description reinforces jobIds, projectId, timeoutSeconds, and untilPlaceable, but most of the parameter meaning is already present in the schema.

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 begins with a specific verb and resource: 'Wait for jobs you started, all in one call.' It distinguishes several job categories and explains what the tool returns, making it easy to separate from siblings such as wait_for_asset.

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?

It explicitly tells the agent to pass every Job ID, to call wait_for_jobs again for jobs still running, and never to start a job again to get its result. It also names wait_for_asset as the alternative for outputs that are not placeable yet.

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

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

Resources