Skip to main content
Glama

create_transition

Apply a fade, wipe, or cut transition to a specified shot in a new timeline, then export the result to an output file for video editing.

Instructions

Apply a supported fade, wipe or cut transition in a new timeline.

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": {
      "timeline": "<timeline>",
      "shotIndex": "<shotIndex>",
      "output": "<output>"
    },
    "name": "create_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputYes
timelineYes
shotIndexYes
transitionNofade

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already declare readOnly=false, idempotent=false, destructive=false, and openWorld=false, so the safety profile is covered. The description adds nothing beyond that: it doesn't explain the side effect on the referenced timeline, whether a new timeline is produced versus modified, or what happens on repeat calls despite idempotentHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, which is structurally clean. However, its brevity comes at the cost of under-specification rather than genuine economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described. Still, for a non-idempotent mutation tool with four parameters at 0% schema coverage, the description leaves critical gaps around effects, constraints, and parameter roles.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning, but it only echoes the transition enum values already present in the schema. The three required parameters (timeline, shotIndex, output) get no explanation, notably shotIndex's 0-29 range and what 'output' denotes.

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?

The description gives a specific verb and resource ('Apply ... transition') and enumerates the supported kinds (fade, wipe, cut), so the core action is unambiguous. It stops short of distinguishing this from other creation tools or clarifying whether 'in a new timeline' means it creates a timeline or operates on the one passed in.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. The word 'supported' implies constraints (e.g., certain transition types or media) but never states them, leaving the agent to guess at valid contexts.

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