List all standard and Quick Export render presets available in DaVinci Resolve, returning JSON to help choose export settings.
List all available render presets (both standard and Quick Export).
Returns JSON with standard render presets and Quick Export presets.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v2.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must bear the full burden. It states the tool returns JSON with preset details, which implies a read-only operation, but it does not explicitly claim non-destructive behavior or disclose any potential side effects or prerequisites. The description is adequate but not fully transparent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise and front-loaded with the primary purpose. It consists of two short sentences, though there is slight redundancy in repeating 'standard and Quick Export' in both sentences. It is still efficient and easy to scan.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given zero parameters and the presence of an output schema, the description is complete. It clearly states what the tool does and what it returns. There are no missing details needed for an agent to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has zero parameters, so there are no semantics to explain. The baseline for 0 parameters is 4, and the description doesn't need to add parameter information. It correctly focuses on output.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool lists all available render presets, explicitly mentioning both standard and Quick Export types. This makes the resource and scope unambiguous, distinguishing it from other list tools like list_projects or list_timelines.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit guidance about when to use this tool versus alternatives. The purpose implies it is used to retrieve render presets, but no context is given such as 'before rendering' or 'to check available options'. It falls short of explicit usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.