Framevine

Redo generation

redo_generation

Generate another take of an existing image or video node, reusing its original inputs and settings (use generate_image/generate_video for a new prompt from scratch). Optionally override the prompt, modelKey or image quality. Spends credits. Returns immediately with a new nodeId and status; poll get_generation_status until it is COMPLETED or FAILED.

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": {
      "threadId": "<threadId>",
      "nodeId": "<nodeId>"
    },
    "name": "redo_generation"
  }
}

Input Schema

Name	Required	Description
`nodeId`	Yes	The node to redo.
`prompt`	No	Optional replacement prompt. Defaults to the original prompt.
`quality`	No	Optional image quality. Defaults to the original quality.
`modelKey`	No	Optional model key from list_models. Defaults to the original model.
`threadId`	Yes	Thread containing the node.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only cover the safety profile (not read-only, not idempotent, not destructive); the description adds what they cannot: the operation spends credits, is asynchronous ("returns immediately with a new nodeId and status"), and requires polling a specific sibling until a terminal state. That is the exact context needed to avoid misusing a non-idempotent paid operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the core action, then the alternative-tool routing, then cost and async/poll semantics. Nothing is repeated from the schema and every sentence carries new 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?

For a non-idempotent, credit-consuming async mutation with no output schema, the description covers the essentials: what it returns (a nodeId plus status) and how to reach a terminal result (poll get_generation_status). Nothing an agent needs before calling is missing.

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 description coverage is 100%, so the baseline is 3; the description earns credit by framing prompt/modelKey/quality as a coherent optional-override set that falls back to the original node's values, which clarifies intent beyond the per-field schema text. It does not add format or constraint detail (e.g. the 2000-char prompt cap) beyond 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?

States a specific verb and resource ("Generate another take of an existing image or video node") plus the defining scope: reusing the original inputs and settings. It explicitly distinguishes itself from generate_image/generate_video, so an agent can pick between them without opening schemas.

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?

Gives an explicit when-to-use rule and the sibling alternative for the other case: use this to re-take an existing node, use generate_image/generate_video for a new prompt from scratch. It also spells out the follow-up obligation (poll get_generation_status until COMPLETED or FAILED).

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

All Framevine 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?