Skip to main content
Glama

set_render_settings

Configure DaVinci Resolve Deliver page renders by loading a preset, setting format, codec, render mode, and output options like target directory, frame range, resolution, and frame rate.

Instructions

Prepare the Deliver page: load a render preset, set format + codec (e.g. 'mov' + 'ProRes422HQ'), render mode, and render settings such as TargetDir, CustomName, SelectAllFrames, MarkIn, MarkOut, FormatWidth, FormatHeight, FrameRate, VideoQuality, ExportAudio, ColorSpaceTag... (see get_api_type('RenderSettings')). Applied in that order.

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": "set_render_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
codecNo
formatNo
presetNo
settingsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare that the tool is not read-only, not destructive, and not open-world. The description adds useful behavioral context by saying settings are applied in a specific order and pointing to get_api_type('RenderSettings') for the full settings schema, but it does not disclose persistence, override behavior, or whether omitted settings are left unchanged.

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 dense but front-loaded with the main purpose and application order. The parenthetical reference and ellipsis are efficient, though the long settings list makes it slightly hard to scan.

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 mutation tool with no output schema, the description gives enough context to invoke it: the Deliver-page purpose, the application order, and a reference for the full RenderSettings type. It could be stronger by documenting mode values and replacement semantics, but it is largely complete.

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 description coverage is 0%, so the description must carry parameter meaning. It does substantial work by explaining format+codec examples, render mode, and many RenderSettings keys such as TargetDir, MarkIn, MarkOut, and FrameRate, though it still omits the mode enum values and exact semantics of preset versus settings.

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 action and resource: preparing the Deliver page by loading presets and setting format, codec, mode, and render settings. It clearly distinguishes this configuration step from sibling tools like add_render_job or start_render, though it does not explicitly name those alternatives.

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?

The phrase 'Prepare the Deliver page' implies this should be used before adding or starting render jobs, but there is no explicit when-to-use or when-not-to-use guidance. It also does not state whether existing settings are replaced or merged.

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

Deploy Server

Other Tools