Skip to main content
Glama

recover_video_remake

Idempotent

Recover an existing cloud video remake in the current project without another generation or generation charge. First read track_progress. On the user's request to continue a failed finish, retry_finish requires canRetryFinish=true and its revision; repeated calls with that revision reuse the accepted continuation. Then track the same jobId. prepare_download queues retrieval of the existing original file when storage previously failed; it never generates or charges again. Read recovery status on the same task; failed recovery is not automatically retried. download returns a short-lived ChatCut file link only when a saved output exists. outputStage=raw_generation means source audio and timing have NOT finished; never present it as the finished remake. No automatic paid resubmission. If recovery is unavailable, report that limitation rather than guessing another route.

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": {
      "action": "<action>",
      "workflowRunId": "<workflowRunId>"
    },
    "name": "recover_video_remake"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
revisionNoRequired for retry_finish: the exact revision returned by track_progress.
projectIdNoProject for this call (full ID or unambiguous prefix). Explicit-timeline calls never change the target of later calls; legacy project selection applies otherwise.
timelineIdNo
workflowRunIdYesOriginal remake workflow jobId from track_progress.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that no generation charge occurs, that repeated calls with the same revision reuse the accepted continuation, that download links are short-lived, that failed recovery is not auto-retried, and that outputStage=raw_generation means audio/timing are unfinished. The only gap is that it does not say what a successful retry_finish or prepare_download response contains, though the no-output-schema situation makes that a minor omission.

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 purpose and the no-charge guarantee, then organized by action. It is dense and telegraphic in places ('Read recovery status on the same task'), but nearly every sentence carries operational meaning; only the repeated no-charge/no-resubmission statements are slightly redundant.

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 multi-step recovery tool with five parameters and no output schema, the description covers sequencing, preconditions, idempotency, and the raw_generation caveat. It stops short of describing return payloads for each action, but the critical decision inputs an agent needs are present.

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 60%, and the description compensates by explaining the semantics of each action value and tying revision to track_progress output and workflowRunId to the original jobId. projectId and timelineId are left to the schema, which does document them, so the remaining gap is small.

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 ('Recover an existing cloud video remake in the current project') plus the key differentiator from submit_video_remake: no new generation or charge. The three action modes are named, so an agent can distinguish this from the sibling submit tools immediately.

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 sequences usage: read track_progress first, use retry_finish only when canRetryFinish=true and with the exact revision, use prepare_download when storage previously failed, use download only when a saved output exists. It also states the fallback ('If recovery is unavailable, report that limitation rather than guessing another route'), which is a clear when-not rule.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.