MCPaeroedu

Official

Overview Schema Source Related Servers Discussions Admin

aeroedu_davinci_timeline_export

Set up a render job in DaVinci Resolve to export a timeline. Choose output path, format, codec, and preset. Then use a separate tool to start rendering.

Instructions

Thiết lập render job trong Resolve Deliver page. Hỗ trợ format: mp4 (H264/H265), mov (ProRes), prores, dnxhd. Sau khi gọi tool này, dùng aeroedu_davinci_render_start để bắt đầu render.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "output_path": "<output_path>"
    },
    "name": "aeroedu_davinci_timeline_export"
  }
}

Input Schema

Name	Required	Description	Default
`output_path`	Yes	Đường dẫn đầy đủ file output. Ví dụ: /Users/pixidev/Movies/output/bai-giang-final.mp4
`format`	No	Format xuất: mp4 (H264), mov/prores (ProRes422HQ), h265, dnxhd	mp4
`codec`	No	Override codec (tuỳ chọn). Ví dụ: H265, ProRes4444, DNxHR HQX
`timeline_name`	No	Tên timeline. Bỏ trống = timeline hiện tại
`preset`	No	Tên Render Preset đã lưu trong Resolve (nếu có)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.0Jun 22, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations do not indicate destructive or idempotent behavior. The description clarifies it only sets up, not renders, but lacks details on side effects like overwriting existing jobs or required project state. Some transparency but incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise: two sentences, no redundant information. It front-loads the primary action and then lists formats and the follow-up call. Every sentence adds value.

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?

Covers the basic purpose and follow-up but omits important context like whether it modifies existing render jobs, required project state, or if multiple calls create duplicates. Given no output schema and sparse annotations, more completeness is needed.

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 100%, so the schema already documents all parameters. The description adds a brief mention of formats but no additional semantics beyond what the enum and parameter descriptions provide.

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 the tool's purpose: setting up a render job in Resolve Deliver page. It lists supported formats and distinguishes itself from the sibling 'aeroedu_davinci_render_start' by specifying the follow-up action.

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?

Provides explicit guidance to use 'aeroedu_davinci_render_start' after calling this tool. However, it does not mention prerequisites or alternative tools; the only related sibling is addressed, so it is moderately helpful.

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