Skip to main content
Glama

export_edit

Start a production export for an edit. Creates an export record, calls export-project-v2, and returns an export ID promptly. Poll get_export until completed for final video URLs. Equivalent requests reuse their existing export. Standard encoding has no additional generation-credit charge and requires existing export access. Optional HDR/upscaling may be billed separately and need their own quote and approval.

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": {
      "workspaceId": "<workspaceId>",
      "editId": "<editId>"
    },
    "name": "export_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
editIdYesThe edit ID
exportIdNoOptional existing export document ID to use
editTitleNoOptional denormalized edit title for the export record
watermarkNoWhether to render a watermark
exportTypeNoExport formatmp4
workspaceIdYesThe workspace ID
exportSettingsNoFine-grained codec, resolution, framerate, HDR, upscale, and audio settings

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / exportType / enum
      Previous value: -[
      -  "mp4",
      -  "zipped_project",
      -  "capcut",
      -  "premiere"
      -]New value: +[
      +  "mp4",
      +  "zipped_project",
      +  "capcut",
      +  "premiere",
      +  "resolve"
      +]
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses the async contract (creates a record, invokes export-project-v2, returns an ID promptly), idempotent deduplication of equivalent requests, an access prerequisite ("requires existing export access"), and a billing split between standard encoding and optional HDR/upscale passes needing separate quote and approval. It omits failure modes, cancellation, and whether the export record is mutable or deletable, which keeps it short of a 5.

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?

Front-loaded with the core action, then the async contract, then the polling alternative, then cost/access constraints — a sensible ordering with no filler sentences. It is dense to the point of being five packed clauses, but each clause carries distinct operational information.

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 an async mutation tool with no output schema and no annotations, the description covers the essential lifecycle (start, returned ID, poll via get_export) plus cost and permission prerequisites. It does not describe what the export record contains or how errors surface, which are the remaining gaps for a tool of this complexity.

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 100%, so every parameter including the nested exportSettings fields is already documented, and the baseline of 3 applies. The description adds only indirect meaning — that HDR and upscaling settings trigger separate billing and approval — without clarifying editId vs exportId reuse or how exportSettings interacts with exportType.

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?

States a specific verb and resource ("Start a production export for an edit") and immediately disambiguates from the sibling by noting it returns an export ID promptly while get_export is for polling. An agent can distinguish this from get_export, analyze_export_ip, and the edit-mutation tools without opening any schema.

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?

Explicitly routes the follow-up step to get_export ("Poll get_export until completed for final video URLs") and explains that equivalent requests reuse an existing export, which prevents redundant calls. It does not state when NOT to use it (e.g., when an export already exists and should be retrieved rather than started), leaving a small gap.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.