Skip to main content
Glama

generate_shot_video

Generate a video from one existing shot still and attach it to that shot. Use approved settings, maxCostUsd and a stable idempotencyKey. Retries reuse the original generation and attachment without overwriting subsequent timeline edits. Keep the result inside the edit.

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": "generate_shot_video"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoVideo model ID. Uses the edit default when omitted.
editIdYesThe edit ID
promptNoMotion prompt. Defaults to the shot videoPrompt when omitted.
shotIdYesThe shot that should receive the generated video
volumeNoAttached shot-video volume. Keep 0 when narration or a separate mix owns the audio.
durationNoGenerated source duration in seconds, chosen independently of the final trimmed timeline duration. Use supported model settings and set source trims with update_shot.
approvalIdNoCombined production approval ID returned by set_proposal_status.
maxCostUsdNoMaximum charge for each output. Checked against authoritative pricing before generation.
resolutionNoOutput resolution supported by the selected model, for example 720p or 1080p.
aspectRatioNoAspect ratio. Uses the edit default when omitted.
workspaceIdYesThe workspace ID
approvalJobIdNoExact production jobId covered by that combined approval.
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.
deferAttachmentNoKeep the current shot video until this replacement completes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / deferAttachment
      Added value: +{
      +  "description": "Keep the current shot video until this replacement completes.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / modelSettings
      Added value: +{
      +  "additionalProperties": {
      +    "anyOf": [
      +      {
      +        "type": "string"
      +      },
      +      {
      +        "type": "number"
      +      },
      +      {
      +        "type": "boolean"
      +      }
      +    ]
      +  },
      +  "description": "Model-specific controls using keys and options from get_model_catalog inputConstraints.slots or variantSelector.",
      +  "type": "object"
      +}
  3. Changed4 schema fields changed
    • addedInput schema / properties / approvalId
      Added value: +{
      +  "description": "Combined production approval ID returned by set_proposal_status.",
      +  "type": "string"
      +}
    • addedInput schema / properties / approvalJobId
      Added value: +{
      +  "description": "Exact production jobId covered by that combined approval.",
      +  "type": "string"
      +}
    • addedInput schema / properties / idempotencyKey
      Added value: +{
      +  "description": "Stable request key. Retries with the same key reuse the existing output and do not start another paid generation.",
      +  "maxLength": 250,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / maxCostUsd
      Added value: +{
      +  "description": "Maximum charge for each output. Checked against authoritative pricing before generation.",
      +  "maximum": 10000,
      +  "minimum": 0,
      +  "type": "number"
      +}
  4. Changed1 schema field changed
    • changedInput schema / properties / duration / description
      Previous value: -"Generated source duration in seconds. It must cover the shot editorial duration."New value: +"Generated source duration in seconds, chosen independently of the final trimmed timeline duration. Use supported model settings and set source trims with update_shot."
  5. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that retries reuse the original generation and attachment without overwriting subsequent timeline edits, and that generation is paid — but a large part of this overlaps the schema's own idempotencyKey and maxCostUsd descriptions, and it omits permissions, async/long-running behavior, and what happens to the existing shot video on failure.

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?

Four short sentences, front-loaded with the core action and then the safety/idempotency constraints. The closing line 'Keep the result inside the edit' is vague but occupies little space.

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 15-parameter, nested-object mutation tool with no annotations and no output schema, the description covers the main workflow and cost/idempotency contract but leaves out approval prerequisites, failure/replacement semantics, and whether the call is synchronous. Adequate but with clear gaps.

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 description coverage is 100% across 15 parameters, so the schema already documents model, prompt, duration, resolution, deferAttachment, and approval fields. The description only references maxCostUsd and idempotencyKey, adding no meaning beyond the schema, so 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: 'Generate a video from one existing shot still and attach it to that shot.' It also names the scope ('inside the edit'), which separates it from the generic generate_video and from image-only siblings such as regenerate_shot_image.

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

Usage Guidelines3/5

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

Gives operational guidance ('Use approved settings, maxCostUsd and a stable idempotencyKey'), implying a prior approval flow, but never states when to choose this tool over generate_video or an alternative path. There are no explicit exclusions or prerequisites spelled out.

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.