Skip to main content
Glama

import_take

Add existing video recordings to a session as takes without editing session.json. Automatically names, numbers, reads length, and lists them; supports single or multiple takes.

Instructions

Add recordings that already exist (e.g. from QuickTime, a phone, a download, or files placed in the session folder) to a session as takes. Never edit session.json by hand: this names the file take-NN-[name-]camera., gives it the next take number, reads its length and lists it. One take: path (+ screen_path for its screen recording). Several: takes=[{path, screen_path, name, keeper}], one take each, in order. Files outside the session are copied (move=true moves them); files already in the session folder are renamed in place.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
moveNoMove files instead of copying them. Default false.
nameNoName for the take.
pathNoThe camera (or only) video file of one take.
takesNoSeveral takes: [{path, screen_path, name, keeper, kind}], one take each, in order.
keeperNotrue stars the take as the keeper.
sessionYesSession as 'Project/folder', an absolute path, or its id (from get_session). An old path still works after a rename or move.
screen_pathNoOptional: the screen recording of the same take.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Adds substantial behavior beyond the annotations: the exact file naming scheme (take-NN-[name-]camera.<ext>), automatic take numbering, reading length, and in-place rename vs copy semantics. Annotations only cover the safe-write profile; the description discloses what actually happens to the caller's files, which is the key risk.

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?

Front-loads the purpose, then the naming/behavior, then the two invocation modes, then file handling. Dense but every sentence carries information; the session.json warning is a useful guardrail rather than 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 write tool with no output schema, it covers naming, numbering, list behavior, and copy/move semantics adequately. It is slightly light on failure modes (duplicate names, missing files) but complete enough for correct invocation.

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 the schema already documents each field, setting a baseline of 3. The description goes further by clarifying the mutually exclusive one-take (path/screen_path) vs. multi-take (takes=[...]) calling conventions and the meaning of move, adding real value over the schema.

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 and resource ('Add recordings that already exist ... to a session as takes') with concrete examples (QuickTime, phone, download). It clearly distinguishes itself from siblings like add_broll, save_broll, and rename_take by describing the import-and-name behavior.

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?

Gives a clear condition for use ('recordings that already exist') and an explicit anti-pattern ('Never edit session.json by hand'), plus the copy-vs-move rule. It does not, however, name sibling alternatives such as add_broll or save_broll, so the routing guidance is implied rather than explicit.

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