Skip to main content
Glama

quick_export

Render the current timeline with a chosen preset such as H.264, ProRes, or YouTube, and optionally toggle whether that preset appears in the export panel.

Instructions

Render the current timeline with a Quick Export preset (e.g. 'H.264', 'ProRes', 'YouTube'). enable_preset toggles whether a render preset appears in Quick Export instead.

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": {
      "preset": "<preset>"
    },
    "name": "quick_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetYes
target_dirNo
custom_nameNo
enable_presetNo
enable_uploadNo
video_qualityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations declare it is not read-only, not destructive, and closed-world, so the agent knows it writes something locally. The description does not say what is produced or where (target_dir is never discussed), what happens if the file already exists, or which preset list is valid. The second sentence, about toggling whether a preset appears in Quick Export, describes a UI-visibility setting rather than a render, which muddies rather than clarifies the effect of enable_preset.

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

Conciseness3/5

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

Two sentences is an appropriate length and the primary action is front-loaded, but the second sentence is placed as if it were equal in weight to the render operation and its meaning is unclear, so it does not fully earn its place.

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

Completeness2/5

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

For a 6-parameter render/write tool with no output schema, the definition leaves too much unsaid: output destination and naming, quality semantics, upload behavior, and overwrite handling are all absent. Given the complexity and zero schema coverage, the description should carry far more of the burden.

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

Parameters2/5

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

Schema description coverage is 0%, so the description bears full responsibility for the 6 parameters. It only touches preset (via examples) and enable_preset (ambiguously); target_dir, custom_name, enable_upload, and video_quality get no explanation at all, and no parameter formats or valid ranges are given.

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?

States a concrete verb+resource combination ('Render the current timeline') and gives concrete preset examples ('H.264', 'ProRes', 'YouTube'), so the agent knows exactly what operation is performed. It does not, however, distinguish itself from plausible siblings such as export_timeline or export_project, leaving the alternative-choice ambiguous.

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

Usage Guidelines2/5

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

The phrase 'current timeline' implies the scope, but there is no explicit statement of when to pick quick_export over export_timeline or export_project, and no prerequisites or exclusions are given. The agent must infer routing from the name alone.

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