Skip to main content
Glama

regenerate_shot_image

Destructive

Regenerate the starting image of an existing shot as the next version. Keeps the same shot and image media IDs, preserves previous versions, and selects the new image in the shot on success. Use this for a shot retake or revised shot image. May spend Sequencer credits.

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": {
      "workspaceId": "<workspaceId>",
      "editId": "<editId>",
      "shotId": "<shotId>"
    },
    "name": "regenerate_shot_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoImage model ID. Defaults to the selected start frame model, then project settings.
editIdYesThe edit ID
promptNoFull image generation prompt. Omit to reuse the selected start frame prompt.
shotIdYesThe existing shot that receives the image version
maxCostUsdNoMaximum charge for each output. Checked against authoritative pricing before generation.
resolutionNoOutput resolution from the selected model catalog.
aspectRatioNo
mediaInputsNoNamed media slots from get_model_catalog, for example reference_image_uri or mask_url.
workspaceIdYesThe workspace ID
modelVariantNoVariant value from get_model_catalog variantSelector.options, such as high for Flare quality. Uses the catalog default when omitted.
modelSettingsNoModel-specific controls using keys and options from get_model_catalog inputConstraints.slots or variantSelector.
idempotencyKeyNoStable request key. Retries with the same key reuse the existing output and do not start another paid generation.
negativePromptNo
sourceImageUrlNoPublic HTTP(S) source image/start-frame URL. Use mediaId for workspace images.
expectedMediaIdNoCurrent shot image ID from get_shot. A changed attachment prevents generation.
referenceImagesNoImages to guide generation. Use labels such as person or product and refer to them as @person or @product in the prompt. Each item accepts a workspace mediaId or a public HTTP(S) URL.
sourceImageMediaIdNoWorkspace image to use as the source image/start frame.
expectedVersionNumberNoCurrent selected start frame version from get_shot. A changed selection prevents generation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only say non-read-only, destructive, non-idempotent, open-world. The description adds genuinely useful context beyond that: the same shot and image media IDs are kept, previous versions are preserved, the new image becomes the selected one on success, and the call may spend Sequencer credits. 'Preserves previous versions' refines rather than contradicts destructiveHint, since the shot's selection still changes.

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 short sentences, front-loaded with the action and its guarantees, ending with the cost warning. Nothing is padded and each sentence carries a distinct fact: identity preservation, version retention, selection, and credit spend.

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 costly, state-changing tool with 18 parameters, nested objects, and no output schema, the description covers the essentials an agent needs before committing: what changes, what survives, and that credits are spent. The guard parameters (expectedMediaId, expectedVersionNumber, idempotencyKey) are left to the schema, which is a reasonable division but slightly weakens pre-call awareness of concurrency protection.

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 89% and the schema already explains expectedMediaId, expectedVersionNumber, idempotencyKey, model, and mediaInputs in detail. The description adds only indirect meaning ('keeps the same shot and image media IDs'), which hints at shotId semantics but does not explain any of the 18 parameters directly, so the baseline 3 applies.

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 with scope: 'Regenerate the starting image of an existing shot as the next version.' That distinguishes it from generating a fresh image or editing an arbitrary image, and it tells the agent the output lands as a new version on an existing shot.

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?

'Use this for a shot retake or revised shot image' gives a clear use condition, and the versioning language implicitly separates it from creating new assets. It stops short of naming an explicit alternative (e.g. generate_image or edit_image) or stating when not to use it, so it is clear but not fully routing.

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.