Skip to main content
Glama

insert_effect_clip

Insert generators, Fusion generators, OFX generators, titles, Fusion titles, or empty Fusion compositions into the current DaVinci Resolve timeline at the playhead to add effect clips in place.

Instructions

Insert a generator, Fusion generator, OFX generator, title, Fusion title or an empty Fusion composition into the current timeline at the playhead (e.g. kind='title' name='Text' or 'Scroll'; kind='fusion_title' name='Text+').

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": {
      "kind": "<kind>"
    },
    "name": "insert_effect_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation, and the description adds placement context (at the playhead in the current timeline). It does not disclose important behavioral details for a timeline mutation: whether insertion ripples or overwrites, what is returned, or what errors occur if no timeline is active. Adds some value above the annotations but leaves the core insertion semantics unexplained.

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

Conciseness4/5

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

A single front-loaded sentence: verb, then the resource enumeration, then parenthetical examples. No filler, though the long enumeration plus examples makes it slightly dense for one sentence.

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 two-parameter mutation with no output schema, the description covers what goes where but omits the effects of the call (ripple vs overwrite, resulting clip selection) and the preconditions. Enough to attempt a call, not enough to predict its outcome confidently.

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?

With 0% schema coverage the description must carry parameter meaning, and it partially does: it enumerates the kinds in prose and gives concrete kind/name pairings ('kind=title name=Text', 'kind=fusion_title name=Text+'). However, it never explains what 'name' means for generator/ofx_generator/fusion_generator kinds, whether name is optional for fusion_composition, or what happens on an unrecognized name, so half the parameter space remains opaque.

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?

States a specific verb (insert) and enumerates the exact resource types it handles, matching the schema enum, and pins the location as 'the current timeline at the playhead'. It implicitly separates itself from append/audio insertion siblings, but never names an alternative explicitly, so it stops short of full sibling differentiation.

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?

Usage is implied: use this when you want a generator, title, or empty Fusion comp placed at the playhead. There is no explicit 'use X instead when...' routing, no prerequisites (e.g. an active timeline/project), and no statement about what happens when the playhead sits inside an existing clip.

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