Adobe Edit Quick Cut

Adobe Edit Quick Cut

Produces one AI-edited highlight cut from a source video, working entirely from the user's original request. No follow-up questions — infer the intent and duration from what the user already said, fall back to a sensible default when they said nothing, and deliver a single preview.

Surface note: The default flow uses Adobe's MCP App widgets — the asset_add_file file picker (Step 2) and the asset_preview_file preview (Step 5). Use a step's No-widget fallback only when that widget isn't available on the current surface — decide by availability, not by client name.

How Quick Cut Works — and What to Design Around

video_create_quick_cut is an AI rough-cut tool. Its user_prompt is a description of the video and the kind of result you want (e.g. "interview with a nonprofit for social fundraising"), not a list of pacing directives. It selects moments itself. Key limits, each mapped to a rule below:

Async handling (video_create_quick_cut): A status: "working" response is pending — not a failure and not missing output; never treat it as either. Polling is managed by the widget — wait for its completion event; do not call any poll tool yourself. Only after a completed result — or a terminal failure — do you read the output or apply any fallback.

Tool Reference

Workflow

Step 0 — Initialize Adobe Tools

Call adobe_mandatory_init first.

{ "skill_name": "adobe-edit-quick-cut", "skill_version": "3.0.0" }

Step 1 — Entitlement Check

adobe_mandatory_init confirms the "Adobe for creativity" connector is live. Confirm video_create_quick_cut and asset_preview_file are available. If asset_add_file or asset_preview_file is unavailable on this surface, use that step's No-widget fallback. If a tool result carries an importantNote or "Asset Storage & Display" guidance, it overrides the presentation defaults here.

Step 2 — Get the Source Video

If the user's message already references a Creative Cloud asset (a CC assetId), use it directly. Otherwise — including a raw chat upload or a local file, which isn't usable until it reaches Creative Cloud — get it in first via the picker (or the no-widget staging fallback below):

"Let's create a highlight cut from your video. Start by selecting your file:"

asset_add_file()

Extract assetId (the CC asset ID) from the widget context — the widget injects it on confirmation, so wait for that (don't poll).

video_create_quick_cut requires a CC asset ID (assetId), not presignedAssetUrl.

No-widget fallback (only if asset_add_file is unavailable on this surface) — get the assetId from where the file is. A file already in Creative Cloud is referenced directly by its CC assetId. To stage a local file, use the upload path adobe_mandatory_init routes to for this surface (surfaces differ — it may name a surface-specific upload tool, or the asset_initialize_file_upload → PUT → asset_finalize_file_upload sequence). Staging requires egress — check egress status from adobe_mandatory_init first; if egress is disabled and no picker exists here, tell the user staging isn't possible. For the initialize/finalize sequence: get file size and MIME type, call asset_initialize_file_upload({ path, media_type }), PUT the bytes to the returned URL, then asset_finalize_file_upload({ filename, transfer_document }), and extract the assetId.

Step 3 — Build the Intent from the Original Request (no questions)

Do not ask the user anything. Derive both inputs from their original message.

user_prompt — start from the generic intent, and merge the user's own words only if they gave any:

• Generic intent (default when the user gave no detail):

  An engaging highlight reel of this video that keeps its most compelling, high-energy, and visually interesting moments, with a strong opening and a natural flow, ready to share on social media.

• User gave intent or output details (content, occasion, purpose, a topic focus such as "the parts about pricing", or a vibe such as "cinematic", "hype", "for our fundraiser") — put their description first and keep the highlight framing:

  <user's description>. Edit into an engaging highlight reel that keeps the strongest, most compelling moments with a natural flow, suitable for social sharing. Fold any named vibe adjective ("cinematic", "energetic") into the sentence. If the user's own description already fully specifies the desired output, use it as-is.

target_duration (seconds) — always pass a number:

• User stated a length → use that number. It's a soft target — Quick Cut aims for it but may run slightly over. For an upper bound ("under a minute"), target a few seconds under the cap (e.g. ~50) and note it's approximate; if they need a strict cap or an exact runtime, use video_render instead.
• No length stated → use a 30s default.

Note (API gap): the Quick Cut UI offers Duration: Auto, but the MCP video_create_quick_cut requires a numeric target_duration — so pass the user's length, or the 30s default.

Step 4 — Run One Cut, Then Wait for Completion

video_create_quick_cut({
  assetIds: [assetId],
  target_duration: <stated_length_or_30>,
  user_prompt: "<generic-or-merged intent>"
}) // → taskId

Acknowledge briefly: "Creating your highlight cut — I'll preview it as soon as it's ready."

video_create_quick_cut is async too (returns status: "working"). Wait for the completed result before previewing (see Async handling above) — don't act on a working status. On completion, store outputUrl (the completed presignedAssetUrl). The URL is time-limited — go straight to the preview.

If the completion event never arrives: don't stall or invent a status — the last known state is processing. If a tracker exists but is slow, tell the user the cut is still processing and its preview will appear when it completes; if this surface has no async tracker at all, tell them the cut was submitted and is processing but this session can't retrieve the result, and suggest a widget-capable client such as Adobe Express.