Skip to main content
Glama
Sign In

Framevine

by com.framevine
OverviewDiscussionsAdmin

Add clips to timeline

add_clips_to_timeline
Idempotent

Append generated videos from a thread to its timeline, in the order given. Goes into the active cut unless cutId is given; a first cut is created if the thread has none. Only video nodes that have not failed can be added, and a video already in the cut is skipped. Returns the updated 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": {
      "threadId": "<threadId>",
      "nodeIds": "<nodeIds>"
    },
    "name": "add_clips_to_timeline"
  }
}

Input Schema

NameRequiredDescriptionDefault
cutIdNoCut id from get_timeline (default: the active cut).
cutNameNoName for the new cut if one has to be created (default 'Cut 1').
nodeIdsYesVideo node ids from this thread (see get_thread), in playback order.
threadIdYesThread id, from list_threads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that clips append in the order given, that failed video nodes are rejected, that duplicates already in the cut are skipped, and that it returns the updated timeline. The skip-on-duplicate behavior also explains the idempotentHint=true in concrete terms.

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?

Three tight sentences, front-loaded with the core action, followed by target selection, constraints, and return value. No repetition of the title or schema.

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 four-parameter mutation with no output schema, the description covers the default path, edge cases (failed nodes, duplicates), and the return value. Nothing an agent needs to invoke it correctly is missing.

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 100%, so parameters are already documented; the description nonetheless adds semantic value by explaining the cutId default (active cut) and the implicit cut-creation path tied to cutName. It doesn't elaborate on nodeIds ordering beyond what the schema states.

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?

Uses a specific verb ('Append') on a specific resource ('generated videos from a thread') into a named target ('its timeline'), with ordering semantics stated. Clearly distinguishable from siblings like create_cut, reorder_clips, and remove_clips.

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?

Explains default behavior (active cut unless cutId is given) and the fallback (a first cut is created if the thread has none), which tells the agent when it can omit cutId. It stops short of naming alternative tools for reordering or removing clips, so it's clear context but not a full when-to-use/when-not-to-use map.

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

All Framevine toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources