Skip to main content
Glama

render_job_add

Queues a render job for the current DaVinci Resolve timeline using a preset or format and codec, with optional range, settings, and output directory.

Instructions

Queue a render job for the current timeline. preset: a render preset ('H.264 Master', 'YouTube - 1080p', 'TikTok - 1080p', 'ProRes 422 HQ' …); or format ('mp4','mov','mxf'…) + codec ('H264','H265','ProRes422HQ'…). start/end = range (default whole timeline). settings = extra RenderSettings (FormatWidth, FormatHeight, FrameRate, VideoQuality, ExportAudio, ExportVideo, AudioCodec, AudioBitDepth, ExportAlpha, EncodingProfile, ExportSubtitle, SubtitleFormat 'BurnIn', UseFullExtents, AddFrameHandles …). Output defaults to ~/Documents/ResolveMCP/renders.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "render_job_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNo
nameNo
codecNo
startNo
formatNo
presetNo
settingsNo
target_dirNo
single_clipNo
timeline_nameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses queueing behavior, the default whole-timeline range, default output directory, and key setting names, but it omits execution timing, permissions, validation behavior, and what is returned when a job is queued.

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 definition is front-loaded with the core action and then supplies dense parameter details without much filler. It is a single long paragraph rather than structured bullets, but the content is largely purposeful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter render-queue tool with no annotations and no output schema, the description covers the core workflow and many settings. However, it leaves important parameters unexplained and does not describe job return or execution semantics, so it is adequate but incomplete.

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 0%, so the description must compensate. It explains the central preset/format+codec pattern, start/end defaults, settings keys, and output default, but it does not explain name, timeline_name, single_clip, or explicitly target_dir, leaving several of the 10 parameters undocumented.

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 states a specific verb and resource: "Queue a render job for the current timeline." This clearly distinguishes it from generic render operations, though it does not explicitly contrast it with siblings such as render_start or render_jobs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by "Queue a render job" and the current-timeline scope, but there is no explicit guidance on when to use this instead of render_start, render_jobs, or render_options. Defaults for range and output location are helpful but do not constitute routing guidance.

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