OpenScreen

Official

Overview Schema Source Related Servers Discussions Admin

duplicateClip

Copy a clip directly after itself, including footage, crop, source range, trims, zooms, speed regions, annotations, and camera-fullscreen regions, so edits to each remain independent. Returns clipId.

Instructions

Copy a clip, placed right after it: the same footage, crop and source range, with its own copy of the clip's trims and of the zooms, speed regions, annotations and camera-fullscreen regions on it. Edits to one no longer touch the other. Returns the copy's clipId; moveClip puts it somewhere else.

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": {
      "clipId": "<clipId>"
    },
    "name": "duplicateClip"
  }
}

Input Schema

Name	Required	Description	Default
`clipId`	Yes
`projectId`	No	The project to act on, from listProjects. Omit it only for the project open in the OpenScreen editor, which works only while the app runs.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.1Oct 18, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare this is a non-destructive, non-readonly, closed-world operation, and the description adds substantial value on top: exactly what gets duplicated (footage, crop, source range, trims, zooms, speed regions, annotations, camera-fullscreen regions), the deep-copy independence property, and the returned clipId. It omits permission/error behavior, keeping it from a 5.

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?

The action and placement are front-loaded in the first clause, followed by the copy semantics and return value. It is dense with detail but nearly every clause earns its place; the long enumeration makes it slightly run-on.

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?

With no output schema, the description correctly states the return value (the copy's clipId). Both parameters are accounted for across description and schema, and the copy semantics are fully explained, leaving only minor gaps like failure modes.

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 coverage is 50%: projectId is documented in the schema, but clipId has no schema description. The description confirms clipId is the input (via 'returns the copy's clipId') but adds no format, sourcing, or constraint detail for either parameter, so it only marginally compensates for the gap.

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?

States a precise verb (copy/duplicate) and resource (clip) with placement semantics ('placed right after it'), and distinguishes itself from moveClip, which repositions rather than copies. An agent can differentiate it from siblings like insertClip or moveClip without opening schemas.

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?

The description makes the use case clear (get an independent copy of a clip and everything on it) and names moveClip as the alternative for repositioning. It stops short of explicit when-not guidance, but the context for choosing duplication over editing is well implied by 'edits to one no longer touch the other.'

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