Skip to main content
Glama

add_transition

Adds a transition to the start or end edge of a timeline item, requiring media handles on that edge, and returns the new transition item.

Instructions

Add a transition at the start or end edge of a timeline item (e.g. type 'Cross Dissolve', 'Dip To Color Dissolve', 'Smooth Cut'; category simple / fusion / ofx / audio). The item needs media handles on that edge. Returns the transition item.

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": {
      "item": "<item>"
    },
    "name": "add_transition"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
typeNoCross Dissolve
categoryNosimple
durationNo
positionNostart
alignmentNocenter

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare that this is a non-read-only, non-destructive, non-open-world operation. The description adds useful context about media handles and the return value, but it does not say whether an existing transition is replaced, what permissions are needed, or how duration and alignment affect the result.

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 two tight sentences with the action and scope front-loaded. The example values and prerequisite are included without unnecessary wording.

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

Completeness3/5

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

For a six-parameter mutation tool with no output schema and no parameter descriptions, the definition covers the core action and prerequisite but omits meaningful details about duration, alignment, and replacement behavior. It is adequate but not fully complete.

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 description coverage is 0%, so the description must carry parameter meaning. It explains the item, gives examples for type, enumerates category options, and names start/end positions, but it leaves duration units and alignment semantics unexplained.

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 uses a specific verb and resource: add a transition at the start or end edge of a timeline item. It gives concrete type examples and category values, and states that it returns the transition item, so an agent can distinguish it from sibling tools like add_markers or add_track.

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

Usage Guidelines4/5

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

It clearly states the prerequisite that the item needs media handles on the chosen edge. It does not explain when to choose this over alternative editing approaches, but the core usage condition is explicit.

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

Deploy Server

Other Tools