Skip to main content
Glama

assign_line

Idempotent

Assign a script line to a shot so the shot speaks that line or shows it as a caption, replacing the shot's own voice in one undoable step.

Instructions

Give one shot one script line: the shot speaks that line's voice (or shows its words as a caption until it has one). It replaces the shot's own voice. One undo step. Returns the shot, line and length. To put a whole script into many shots at once, use write_script.

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": {
      "line": "<line>",
      "shot": "<shot>"
    },
    "name": "assign_line"
  }
}

Input Schema

NameRequiredDescriptionDefault
fitNotrue: make the shot as long as the line.
lineYesA line id from get_script.
shotYesA shot id from get_project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.2
    • addedInput schema / properties / fit / description
      Added value: +"true: make the shot as long as the line."
    • addedInput schema / properties / line / description
      Added value: +"A line id from get_script."
    • addedInput schema / properties / shot / description
      Added value: +"A shot id from get_project."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the consequence that matters: it 'replaces the shot's own voice', with a caption fallback until a voice exists. It also states reversibility ('One undo step') and the return payload (shot, line, length), which annotations cannot convey.

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?

Four short sentences, each carrying distinct information: effect, side effect, reversibility, return value, and the alternative tool. Nothing is repeated and the primary effect is front-loaded.

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 three-parameter mutation with no output schema, the description covers what changes, what is overwritten, how to undo, and what comes back. An agent has everything needed to call it correctly and to choose the batch alternative.

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 100% and each parameter already carries a description, including the fit flag's meaning. The narrative explains the voice/caption outcome but never addresses the fit parameter or how it interacts with shot length, so it adds little 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 ('Give one shot one script line') and immediately clarifies the resulting effect: the shot speaks that line's voice or shows a caption. It is clearly distinguishable from the bulk sibling write_script, so an agent can separate the two without opening a 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?

Explicitly routes the agent: single-line assignment here, and 'To put a whole script into many shots at once, use write_script.' The condition that selects the alternative (batch vs single) is stated rather than implied.

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