GenFlick

recover film studio generation

native.recover_film_studio_generation

DestructiveIdempotent

Request a currently legal recovery action for one exact Film Studio generation, preparation run/step, or media-dispatch job. For preparation, retry_unsubmitted resumes unchanged accepted work; keep_existing_board approves only an exact selected board with unavailable original provenance and no reference conflict, then resumes its original unsubmitted video; cancel retires it and preserves completed images; replace accepts one new generation using current settings, only when diagnosis offers it and the creator requested restart/regeneration. Use keep_existing_board only when the creator authorized proceeding with the saved board. Requires the diagnostic state fingerprint. For an accepted batch, retry_unsubmitted resumes admission with the same child identities; accepted provider receipts are preserved. Observation and saved-result apply never resubmit paid work.

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": {
      "work_id": "<work_id>",
      "arguments": "<arguments>",
      "expected_catalog_version": "<expected_catalog_version>",
      "read_skills": "<read_skills>",
      "request_key": "<request_key>"
    },
    "name": "native.recover_film_studio_generation"
  }
}

Input Schema

Name	Required	Description
`work_id`	Yes
`arguments`	Yes
`read_skills`	Yes	Exact required native skills and their dependencies, copied from the accepted session bootstrap's skills array. Include only entries in that array. General mcp.* guides and native.{studio}.instructions are guidance, not native skill proofs.
`request_key`	Yes
`publication_proposal_id`	No	For native Social scheduling, the exact server-approved publication proposal. This identifier cannot confer approval by itself.
`expected_catalog_version`	Yes	For a new session, read a studios/{studio}/native/{pack} child toolset and copy invocation.catalog_version from a native tool descriptor. Do not use the top-level library version. For calls in an existing session, use that session proposal's catalog_version.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already disclose destructive, idempotent, open-world, and non-read-only behavior. The description adds meaningful behavioral detail beyond that: cancel preserves completed images, observation and saved-result apply never resubmit paid work, keep_existing_board requires authorization and exact provenance, and replace is limited to diagnosed and creator-requested cases.

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 purpose is front-loaded and most sentences carry useful constraints or action semantics. The description is dense and semicolon-heavy, but it is appropriately sized for a six-parameter recovery tool with multiple action branches.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex tool with nested arguments and many sibling tools, the description covers the action model and key behavioral safeguards well. It remains incomplete on parameter meanings, request-key usage, skill proofs, and catalog-version requirements, so an agent still needs to rely heavily on the schema.

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?

The description substantially explains the meaning and preconditions of the action enum values, which is valuable beyond the schema. However, it does not explain several other important parameters such as work_id, request_key, expected_version, read_skills, or expected_catalog_version, and schema coverage is only 50%.

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 states a specific verb and resource: requesting a recovery action for one exact Film Studio generation, preparation run/step, or media-dispatch job. It scopes the target precisely enough to distinguish this from broad work or run recovery tools, though it does not explicitly name the nearest sibling alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives actionable conditions for several action choices, including when retry_unsubmitted, keep_existing_board, cancel, and replace are appropriate. It also says a diagnostic state fingerprint is required. The main gap is that it does not explicitly route the agent from diagnosis tools to this recovery tool or compare it with sibling recover tools.

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

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

Resources

Need Help?