CueFrame

Retry Render

retry_render

Re-render an existing render job's FROZEN composition snapshot — it inherits that job's exact composition/intent/priority and queues a fresh renderJob; it does NOT re-read the project's current composition. So it only helps a TRANSIENT failure (the failed render's retryable:true / category:"transient" — a flaky pipeline/infra fault): re-attempting the same snapshot may succeed. For a DETERMINISTIC failure (retryable:false / category:"authoring" — a bad param, an unresolvable media/brand ref), retry_render reproduces the SAME failure: FIX the composition first via apply_composition, then create_render (a retry alone is futile). Check retryable on getRender / wait_job to pick the path. Returns the new render; then wait_job(kind="render", id=).

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": {
      "projectId": "<projectId>",
      "renderId": "<renderId>"
    },
    "name": "retry_render"
  }
}

Input Schema

Name	Required	Description
`renderId`	Yes	renderId (path).
`commandId`	No	Retry identity. A call repeated with the same commandId returns the first result instead of acting twice.
`projectId`	Yes	projectId (path).

Output Schema

Name	Required	Description
`id`	No
`error`	No	Human-readable failure message. Pair with `errorCode` for a stable, machine-readable code an agent runner can branch on.
`engine`	No	The render engine the row was minted for. Null on rows minted before the engine was recorded.
`format`	No	The resolved output format the render was encoded at (aspectRatio, fps, resolution): the frozen composition's, after any create-time scale override. Null on legacy rows.
`status`	No
`listUsd`	No	A2 money stamp: the metered event's LIST price (USD), stamped at the success terminal (exports for deliverable renders, compose_capture for A8 previews). A plan allowance may zero the actual invoice line — this is the list price, never a Stripe charge. Absent while running, on failure, and for x402 orgs (on-chain receipts). Mirrors the get_usage ledger.
`preview`	No	The scoped preview window when this is a preview_clip render; null for a full deliverable.
`category`	No	Failure taxonomy when status is `error`; null otherwise. `authoring` = deterministic defect in YOUR composition/request — fix it, retrying is futile; `transient` = temporary pipeline/infra failure — safe to retry_render; `internal` = unexpected server fault — retry once then escalate. Mirrors the render.failed webhook's `category`.
`progress`	No	Non-terminal render progress; phase is one of the worker's emitted stages.
`warnings`	No	Non-fatal advisories surfaced at render-CREATE (omitted when none, and on GET — create-time only).
`createdAt`	No
`errorCode`	No	Stable, machine-readable error code (e.g. `render_pipeline_unavailable`, `render_route_missing`, `render_pipeline_failed`). Null when status is not `error` or unavailable for an older render.
`outputUrl`	No
`retryable`	No	Whether re-attempting the SAME render can succeed (status `error`); null otherwise. true → call retry_render. false → deterministic (category authoring/internal); fix the composition first — retry_render alone reproduces it. Mirrors the render.failed webhook's `retryable`.
`updatedAt`	No	ISO-8601 timestamp of the render's most recent progress update. Compute staleness = now − updatedAt to distinguish a wedged render from a slow one and decide whether to wait, cancel, or retry.
`completedAt`	No	ISO-8601 instant the render reached its terminal status (complete, error or cancelled); null while it runs. Pair with createdAt for the wall time.
`errorDetails`	No	Structured failure context — `{ targetUrl?, upstreamStatus?, upstreamCode?, attemptedAt? }`. Surfaced so agent runners can distinguish operator-config issues from upstream-down vs route-missing without parsing `error`.
`compositionId`	No	The composition this render froze at create time (the project's active one, or the compositionId the request named). Null on renders minted before this was recorded.
`outputExpiresAt`	No
`outputDurationSec`	No	The output's length in seconds (the composition timeline's, or the preview window's), as billed. Null on legacy rows.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 28, 2026
- addedInput schema / $defs
```
Added value: +{
+  "__schema0": {
+    "maxLength": 128,
+    "minLength": 1,
+    "type": "string"
+  }
+}
```
- addedInput schema / properties / commandId / $ref
```
Added value: +"#/$defs/__schema0"
```
- removedInput schema / properties / commandId / maxLength
```
Removed value: -128
```
- removedInput schema / properties / commandId / minLength
```
Removed value: -1
```
- removedInput schema / properties / commandId / type
```
Removed value: -"string"
```

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / commandId

Added value: +{
+  "description": "Retry identity. A call repeated with the same commandId returns the first result instead of acting twice.",
+  "maxLength": 128,
+  "minLength": 1,
+  "type": "string"
+}

Changed6 schema fields changedOct 18, 2026

addedOutput schema / properties / completedAt

Added value: +{
+  "description": "ISO-8601 instant the render reached its terminal status (complete, error or cancelled); null while it runs. Pair with createdAt for the wall time.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / compositionId

Added value: +{
+  "description": "The composition this render froze at create time (the project's active one, or the compositionId the request named). Null on renders minted before this was recorded.",
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / engine

Added value: +{
+  "description": "The render engine the row was minted for. Null on rows minted before the engine was recorded."
+}

addedOutput schema / properties / format

Added value: +{
+  "description": "The resolved output format the render was encoded at (aspectRatio, fps, resolution): the frozen composition's, after any create-time scale override. Null on legacy rows."
+}

addedOutput schema / properties / outputDurationSec

Added value: +{
+  "description": "The output's length in seconds (the composition timeline's, or the preview window's), as billed. Null on legacy rows.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / preview

Added value: +{
+  "description": "The scoped preview window when this is a preview_clip render; null for a full deliverable."
+}

First observedOct 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only declare the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), but the description adds far more: it inherits the frozen snapshot, queues a fresh renderJob, reproduces deterministic failures identically, and returns the new render. This goes well beyond the annotations and discloses the core behavioral trap (identical reproduction of authoring faults).

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?

Dense and front-loaded with the frozen-snapshot constraint and the failure taxonomy, with the next-step wait_job call at the end. Slightly heavy with em-dash nesting, but every clause carries decision-relevant information.

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, annotations, and full schema coverage are present, and the description still supplies everything an agent needs: failure-condition routing, return value (new render), and the follow-up wait_job call. Nothing essential for correct invocation is missing.

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 parameters (renderId, commandId, projectId) are already documented including commandId's dedup semantics. The description adds no parameter-specific syntax or format detail beyond what the schema provides, so the baseline 3 is appropriate.

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 and resource ('Re-render an existing render job's FROZEN composition snapshot') and immediately distinguishes itself from create_render by noting it does NOT re-read the project's current composition. An agent can tell exactly what this does and how it differs from the sibling that creates a render from current state.

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?

Explicitly states when it helps (transient failure, retryable:true) and when it is futile (deterministic failure, retryable:false), and names the correct alternative path: apply_composition then create_render. It even tells the agent how to check (retryable on getRender / wait_job). This is textbook when/when-not/alternatives guidance.

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

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