Skip to main content
Glama

tail

DestructiveIdempotent

Set, read, or reset the end card/bumper that plays after the last frame of a project.

Instructions

Read or change the finishing pass this project plays after its last frame.

An end card or a bumper, applied by export itself rather than glued on afterward with ffmpeg — the fix for a defect that has already shipped: a finishing pass applied downstream of export is dropped by every derivation at exit 0, silently, because nothing in the project ever knew it existed (HISTORY.md § The bumper the teaser never had, § The end card). Call it with no arguments to read what is in force.

asset must be card:name, never a clip_id — verify diffs a render's own transcription against the timeline's words, and silence adds none of its own, which is exactly what a card behind it guarantees and a media clip would not. seconds is the tail's whole length, card included, not a hold with fade added on top of it (the known trap: xfade finishes exactly at the length it is given). fade is recorded and echoed but not yet drawn — this build cuts to the card hard, at seconds.

Setting asset or seconds for the first time needs both together; either alone after that updates just that field, the same partial-update shape caption_style has. reset drops the tail entirely.

Needs an existing picture cue lane covering the whole film — add cues first (cue_add) if the project does not have one; export names why otherwise. plan resolves and validates without writing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fadeNoRecorded and echoed, not yet drawn: this build cuts to the card hard, at `seconds`.
pathNoThe project directory to act on. Omit it — the usual case — when this server is bound to a project (started as `proofcut -C DIR mcp`, or inside a project; `ping` says which): it then resolves to that one bound project, a relative path resolves against it, and a path outside it is refused by name. Unbound, `path` is the whole address and omitting it refuses rather than guessing.
planNoResolve the whole call and report what it would do, writing nothing. Prefer it over doing the thing and undoing it.
assetNoThe end card or bumper, as `card:name` — never a clip id. `verify` diffs the render's own transcription against the timeline's words, and a card behind silence adds none of its own, which a media clip would.
resetNoDrop the tail entirely. Note a derivation inherits none of it anyway and reports `tail_dropped`.
secondsNoThe tail's **whole** length, card included — not a hold with `fade` added on top of it.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed21 schema fields changedv0.25.0
    • removedInput schema / properties / asset / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / asset / description
      Added value: +"The end card or bumper, as `card:name` — never a clip id. `verify` diffs the render's own transcription against the timeline's words, and a card behind silence adds none of its own, which a media clip would."
    • removedInput schema / properties / asset / title
      Removed value: -"Asset"
    • addedInput schema / properties / asset / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / properties / fade / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / fade / description
      Added value: +"Recorded and echoed, not yet drawn: this build cuts to the card hard, at `seconds`."
    • removedInput schema / properties / fade / title
      Removed value: -"Fade"
    • addedInput schema / properties / fade / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedInput schema / properties / path / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / path / description
      Added value: +"The project directory to act on. Omit it — the usual case — when this server is bound to a project (started as `proofcut -C DIR mcp`, or inside a project; `ping` says which): it then resolves to that one bound project, a relative path resolves against it, and a path outside it is refused by name. Unbound, `path` is the whole address and omitting it refuses rather than guessing."
    • removedInput schema / properties / path / title
      Removed value: -"Path"
    • addedInput schema / properties / path / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • addedInput schema / properties / plan / description
      Added value: +"Resolve the whole call and report what it would do, writing nothing. Prefer it over doing the thing and undoing it."
    • removedInput schema / properties / plan / title
      Removed value: -"Plan"
    • addedInput schema / properties / reset / description
      Added value: +"Drop the tail entirely. Note a derivation inherits none of it anyway and reports `tail_dropped`."
    • removedInput schema / properties / reset / title
      Removed value: -"Reset"
    • removedInput schema / properties / seconds / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedInput schema / properties / seconds / description
      Added value: +"The tail's **whole** length, card included — not a hold with `fade` added on top of it."
    • removedInput schema / properties / seconds / title
      Removed value: -"Seconds"
    • addedInput schema / properties / seconds / type
      Added value: +[
      +  "number",
      +  "null"
      +]
    • removedInput schema / title
      Removed value: -"tailArguments"
  2. First observedv0.24.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already indicate mutability, idempotency, and destructiveness, but the description adds substantial behavioral context: the finishing pass is applied by `export` itself, the fix for a shipped defect, that `fade` is recorded but not drawn (cuts hard at `seconds`), that first-time setting of `asset`/`seconds` requires both together, and that `reset` drops the tail. This goes well beyond the annotation flags.

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?

The description is dense but every sentence earns its place. It front-loads the core purpose, then layers parameter semantics, edge cases, and prerequisites in a logical flow. Bold emphasis on the cue-lane requirement and use of inline code for parameters aid scanning. No fluff or redundancy.

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 tool with six parameters, non-trivial interactions, and integration with `export` and `verify`, the description covers all necessary angles: read/write behavior, partial-update rules, reset semantics, `plan` safety, and prerequisites. It even references HISTORY.md for deeper context. With an output schema present, nothing an agent needs 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.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema descriptions cover all six parameters at 100%, the tool description adds deep meaning beyond them: for `asset`, it explains why it must be `card:name` and the verify rationale; for `seconds`, it clarifies the whole-length semantics and the `xfade` trap; for `fade`, it discloses it's not yet drawn; for `plan`, it says it resolves and validates without writing. These enrich the schema with critical domain logic.

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 description opens with a precise verb and resource: 'Read or change the finishing pass this project plays after its last frame.' It immediately distinguishes itself from siblings like `export` (which applies the pass) and `finish_report` (which likely reports on it). The phrase 'end card or bumper' and 'applied by export itself rather than glued on afterward' clearly define the tool's unique scope.

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 provides explicit guidance on when to use the tool: to read or set the finishing pass. It warns about the `xfade` trap, explains the prerequisite of an existing picture cue lane and directs to `cue_add` if missing, and recommends `plan` to validate without writing. It also clarifies the partial-update semantics and that `reset` drops the tail entirely, leaving no ambiguity about usage.

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