Skip to main content
Glama

quick_export

Render the current timeline using a Quick Export preset, choosing preset, output name, and target directory for direct delivery.

Instructions

Render the current timeline with a Quick Export preset (see render_options quick_export_presets).

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

Input Schema

NameRequiredDescriptionDefault
nameNo
presetNoH.264
target_dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden and discloses almost nothing beyond "render": it does not say whether the operation writes a file, where the output lands by default, whether it blocks or runs asynchronously, whether it requires the project to be saved, or whether existing files are overwritten.

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?

A single front-loaded sentence with no filler, and the cross-reference is placed inline where it is needed. It is under-specified rather than verbose, so length is not the problem.

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?

A zero-required-parameter mutation/rendering tool with no annotations and no output schema needs the description to explain output location, required permissions, and execution behavior. None of that is present, so an agent cannot confidently predict the result of a call.

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 description coverage is 0% across three parameters, so the description must compensate. It only gestures at "preset" (and points elsewhere for valid values); "name" and "target_dir" — which appear to control the output filename and destination — are given no meaning at all, so the compensation is partial at best.

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?

"Render the current timeline with a Quick Export preset" gives a specific verb (render) plus scope (current timeline) and a preset-based mode, which separates it from the other export tools in the sibling list. It stops short of stating how it differs from timeline_export or project_export, which are the closest possible alternatives.

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 only pointer is "see render_options quick_export_presets", which tells an agent where to find preset names, not when to choose this tool over timeline_export, lut_export, or metadata_export. There are no exclusions, prerequisites, or conditions of use.

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