Cutible MCP Server

import_otio

Import an OpenTimelineIO file into the current project to load its timeline, clips, and edits for further editing or review.

Instructions

Import an OpenTimelineIO file into the current project.

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": {
      "otio_path": "<otio_path>"
    },
    "name": "import_otio"
  }
}

Input Schema

Name	Required	Description	Default
`otio_path`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 14, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description must disclose side effects or behavioral traits, but it only says 'import' into the current project. It does not state whether this replaces, appends, or modifies existing timeline data, what permissions are needed, or what happens to the project state.

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 description is a single, front-loaded sentence with no redundant words. It could carry more useful detail, but as written it is concise and readable.

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?

For a mutation-like import tool with no annotations and no output schema, this description is incomplete. It does not mention side effects, return values, or the relationship between the imported file and the current project, leaving an agent without enough context to invoke it confidently.

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 clarify the parameter. It adds that otio_path refers to an OpenTimelineIO file, but it does not explain path format, file extension, supported sources, or any constraints beyond that.

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 clearly states the action ('Import'), the input type ('OpenTimelineIO file'), and the destination ('current project'). It is specific and distinct from siblings like export_otio, though it does not explicitly differentiate itself from ingest_asset or load_project.

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?

The description gives no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It only implies usage when one wants to import an OpenTimelineIO file, but that is not enough to help an agent choose among the many sibling tools.

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