Skip to main content
Glama

import_media

Imports video, audio, stills, or timeline files into a FilmCraft project and returns new project item IDs for use with add_clip, so media can be placed on the timeline.

Instructions

Import media files (video, audio, stills, or EDL/FCP XML/FCPXML/OTIO/AAF timelines) into the project. Returns the new project item ids used by add_clip.

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": {
      "paths": "<paths>"
    },
    "name": "import_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
fpsNoFrame rate of a baked image sequence
bakeNoWith imageSequence: render the sequence to a ProRes .mov next to the frames and import that instead. The app can keep stale frames of a re-written sequence; a baked movie never is.
pathsYes
projectNoPath to the .fcproj project file; omit to edit the FilmCraft app connected with connect_app
imageSequenceNoTreat the first numbered still as an image sequence

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and openWorldHint=false, so the mutation/non-network profile is already covered. The description adds that it returns new project item ids, filling the gap left by the missing output schema. It does not disclose other behavior such as whether media is copied or referenced, duplicate handling, or that changes persist only after save_project.

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?

Two dense sentences, front-loaded with the action and accepted formats, followed by the return value that drives the next step. No redundant restatement of the tool name or filler.

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?

For a five-parameter mutating import tool with no output schema, the description covers what is imported and what comes back, which is what an agent needs to chain into add_clip. It leaves out persistence/save semantics and copy-vs-reference behavior, which are relevant but partly addressable via the project parameter.

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 80%, so most parameters (fps, bake, project, imageSequence) are already documented in the schema. The description names no parameters and adds no semantics beyond the schema, so the baseline 3 for high-coverage schemas applies.

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 specific verb ("Import") and resource ("media files") and enumerates the accepted formats, including timeline interchange formats. It also distinguishes the tool from add_clip by explaining that the returned item ids are what add_clip consumes, so an agent can place it in the workflow without opening sibling 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 workflow context clear by tying the return value to add_clip, which tells the agent this is the ingestion step before editing. It stops short of naming alternatives or exclusions (e.g., using ffmpeg_convert first, or probe_media to inspect a file before importing).

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