Skip to main content
Glama

Revise one scene of a rendered video

autoshort_revise_scene

Revise one scene in an already rendered video by creating a new draft with the updated visual or narration; the original stays untouched and no charge applies until rendering.

Instructions

Change one scene of a video that was already rendered. Creates a NEW draft that copies every scene (unchanged scenes keep their existing images) with this scene changed; the original video is untouched and nothing is charged. Show it to the user, then autoshort_render_draft renders it as a new, fully charged video (narration re-voiced, video re-assembled). Single-scene re-render inside the existing file is not available yet.

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": {
      "videoId": "<videoId>",
      "scene": "<scene>"
    },
    "name": "autoshort_revise_scene"
  }
}

Input Schema

NameRequiredDescriptionDefault
sceneYes1-based scene number.
visualNoNew shot description; null clears it.
videoIdYes
narrationNoNew narration, read verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.3.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, idempotentHint=false — a bare safety profile. The description goes well beyond: it explains that a new draft is created, unchanged scenes retain existing images, the original video is untouched, and nothing is charged at this step, while the subsequent render is 'fully charged' with re-voiced narration. For a non-idempotent write, that cost and side-effect disclosure is exactly the missing context.

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 core action and its non-destructive/zero-cost nature are front-loaded, and every sentence carries distinct information. The semicolon-chained middle sentence is dense but not redundant; only the trailing 'not available yet' caveat is slightly tangential, though it still prevents a wrong invocation.

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?

With no output schema and four parameters, the description supplies what an agent actually needs: the draft-not-in-place semantics, the credit boundary between this call and render, the required human-in-the-loop step, and the unavailable capability. Nothing needed to call it correctly is missing.

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 75% and the schema already documents 1-based scene numbering, the null-clears behavior of visual, and verbatim narration. The description adds no parameter-level detail (e.g., nothing about videoId or how visual/narration interact with the copied scenes), so it sits at the baseline for well-covered schemas.

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?

The first sentence names a specific verb and resource ('Change one scene of a video that was already rendered'), and the second clarifies the mechanism ('Creates a NEW draft that copies every scene'). This is immediately distinguishable from autoshort_render_draft, autoshort_draft_video, and the generate_* siblings without opening any schema.

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?

The description gives an explicit sequencing rule ('Show it to the user, then autoshort_render_draft renders it') and an explicit exclusion ('Single-scene re-render inside the existing file is not available yet'). Both the when and a named alternative are stated outright, leaving nothing to inference.

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