Skip to main content
Glama

create_dailies

Import camera rolls, create timelines, apply color grades, and sync audio for dailies in DaVinci Resolve.

Instructions

Full dailies pipeline: import camera rolls, create timelines, apply grades, sync audio.

For each camera roll path:

  1. Extract roll name and detect camera letter from the path

  2. Create OCF/{cam}-Cam/{roll_name} bin structure in the media pool

  3. Scan directory recursively for video files

  4. Import clips using batch-first with individual fallback

  5. Create a timeline from the imported clips in a Timelines bin

Optional post-processing:

  • drx_path: Switch to color page and apply DRX grade to all timeline clips

  • cdl_path: Parse CCC or EDL file, match CDL values to clips, apply grades

  • lut_name: Search standard LUT paths and apply to all timeline clips

  • audio_path + sync_audio: Scan for audio files, import to Audio bin, auto-sync

Args: camera_roll_paths: List of absolute paths to camera roll directories. drx_path: Optional path to a DRX grade file to apply. cdl_path: Optional path to a CCC or EDL file with CDL values. lut_name: Optional LUT filename to search for and apply. audio_path: Optional path to directory containing audio files. sync_audio: Whether to auto-sync imported audio. Requires audio_path. timeline_prefix: Optional prefix for timeline names.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cdl_pathNo
drx_pathNo
lut_nameNo
audio_pathNo
sync_audioNo
timeline_prefixNo
camera_roll_pathsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description discloses pipeline steps, batch-first import with fallback, and post-processing effects. However, it omits error handling and destructive actions.

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 structured with steps and bullet points, front-loaded with an overview. While verbose, the length is justified by the tool's complexity.

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?

Given 7 parameters, 1 required, and an output schema present, the description covers the full pipeline, optional steps, and inter-parameter dependencies (e.g., audio_path for sync_audio).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%; the description adds full meaning for each parameter (e.g., drx_path: 'Switch to color page and apply DRX grade'), compensating completely.

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?

The description clearly states 'Full dailies pipeline' and enumerates steps, distinguishing it from sibling tools like import_camera_roll, apply_drx_grade, auto_sync_audio by being a composite workflow.

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 explains when to use this tool for complete dailies processing and details optional post-processing, but does not explicitly mention when not to use or list alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DigitalWorkflowCompany/resolve-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server