ChatCut

export_motion_graphic_prores

Export one or more motion graphics as transparent ProRes 4444 .mov renders.

External MCP ProRes rule: this starts one cloud ProRes render per target and requires the ProRes entitlement. For batches, export only the MGs needed for the requested NLE/XML handoff.

Use this for the manual-equivalent "Export motion graphic" workflow and before NLE XML export when the XML should reference rendered motion-graphic media. The tool starts a cloud render and returns a durable renderId; use track_export with that renderId to wait for completion, then download through /api/v1/jobs/renders/{renderId}/download.

Pass itemId / itemIds when timeline instances should be exported exactly as previewed, including propertyOverrides. Pass assetId / assetIds for media-pool motion graphics; by default the backend will use the first timeline instance of each asset when one exists, matching the editor's media-pool export behavior. Use filenameMode="xml" when preparing motion graphics for submit_export format="xml", because XML references mg-.mov filenames.

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

Input Schema

Name	Required	Description
`name`	No	Optional base filename for filenameMode=asset. .mov is added automatically.
`itemId`	No	Motion-graphic timeline item id or prefix. Prefer this when exporting a specific edited instance.
`assetId`	No	Motion-graphic asset id or prefix. Required when itemId is omitted.
`batchId`	No	Reuse the batchId returned with a batch quote when approving that exact selection.
`itemIds`	No	Motion-graphic timeline item ids or prefixes for a batch export. Each item starts its own ProRes render.
`assetIds`	No	Motion-graphic asset ids or prefixes for a batch export. Use itemIds instead when timeline instance overrides matter.
`projectId`	No	Project for this call (full ID or unambiguous prefix). Explicit-timeline calls never change the target of later calls; legacy project selection applies otherwise.
`timelineId`	No	Optional timeline id/prefix to resolve itemId or the first timeline instance. Omit for the active timeline.
`cloudQuoteId`	No	The real cloud quote for the selected motion graphic or complete batch. Show it before starting; a free quote needs no additional confirmation.
`filenameMode`	No	asset = user-friendly asset-name .mov; xml = mg-<renderKey>.mov for submit_export XML compatibility. Defaults to asset.
`confirmCloudCharge`	No	True only after the user explicitly confirms this exact nonzero credit charge.
`preferTimelineInstance`	No	When assetId is used, export the first timeline instance's property overrides if present. Defaults to true.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

First observedNov 5, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the annotations, which only say it is not read-only and not idempotent. The description discloses that it starts one cloud render per target, requires a ProRes entitlement, involves a nonzero credit charge tied to cloudQuoteId/confirmCloudCharge, and returns a durable renderId rather than a finished file. That is exactly the operational context an agent needs before committing spend.

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-loads the one-line purpose, then layers rules, workflow, and parameter guidance in short paragraphs that each carry distinct information. It is dense for a tool definition and the 'External MCP ProRes rule' framing is slightly verbose, but nothing is filler.

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

Completeness5/5

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

For a 12-parameter, zero-required, no-output-schema, charge-incurring mutation tool, the description supplies the missing pieces: entitlement requirement, cost confirmation, return value (renderId), and the downstream tracking/download steps. An agent could call this correctly and safely without further context.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real selection logic: itemId/itemIds preserve timeline-instance propertyOverrides, assetId/assetIds fall back to the first timeline instance, and filenameMode="xml" exists specifically so submit_export format="xml" can reference mg-<renderKey>.mov files. The only minor gap is it does not explain how batchId relates to cloudQuoteId beyond the schema text.

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?

Opens with a specific verb and resource plus an exact output format: "Export one or more motion graphics as transparent ProRes 4444 .mov renders." It also names the boundaries against sibling tools (submit_export for XML, track_export for polling), so an agent can separate it from export and tracking tools without reading the schema.

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

Usage Guidelines5/5

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

Explicit about when to use it (manual 'Export motion graphic' equivalent, and before NLE XML export), when to use filenameMode="xml", and how to route batches ('export only the MGs needed for the requested NLE/XML handoff'). It also provides the follow-up chain: track_export with the renderId, then the /api/v1/jobs/renders/{renderId}/download path.

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

All ChatCut tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.