Skip to main content
Glama

fade

Create opacity keyframes to bring a clip in from black or out to black over N frames, including sequence ends where Dip to Black may cut; audio clips use Constant Power.

Instructions

Fade a clip in from black or out to black over N frames with opacity keyframes (works at the very end of a sequence, where Dip to Black can cut instead of fade). Audio clips get a Constant Power fade.

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": {
      "clip": "<clip>",
      "edge": "<edge>"
    },
    "name": "fade"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipYesTimeline clip id (from list_timeline)
edgeYes
framesNo
projectNoPath to the .fcproj project file; omit to edit the FilmCraft app connected with connect_app

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and openWorldHint=false, so the description must carry behavior, and it does: it discloses the keyframe-based mechanism and a non-obvious divergence (audio clips get a Constant Power fade). It stops short of saying whether pre-existing opacity keyframes are overwritten or what happens if frames exceeds remaining clip length.

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?

Two sentences, front-loaded with the core operation, and the parenthetical and audio note each add distinct information rather than restating the name. No wasted wording.

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 mutating clip tool with no output schema, it covers mechanism, audio-specific behavior, and the edge case motivating its use. Missing only edge-case semantics around overwriting existing keyframes and frame counts beyond clip length.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

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

Schema coverage is only 50% — edge and frames carry no schema descriptions. The description compensates: 'in from black or out to black' explains the edge enum, and 'over N frames' explains the frames parameter, while the schema itself covers clip (via list_timeline) and project.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a concrete verb (fade) plus resource (clip), states both directions (in from black / out to black) and the mechanism (opacity keyframes). It implicitly separates itself from the transition sibling via the 'Dip to Black' comparison, but never names add_transition, so the sibling routing is inferred rather than stated.

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?

Provides one useful scenario hint — use at the very end of a sequence where Dip to Black may cut instead of fade — which implies an alternative. It gives no explicit 'use this instead of X' routing, no prerequisites (clip must exist in the timeline), and no when-not-to-use guidance.

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