Issue 1 — exportResolution rejects 1080/1440/2160

create_clips's schema lists exportResolution as accepting 720 | 1080 | 1440 | 2160, but the server only accepts 720. Passing 1080, 1440, or 2160 (as a JSON number, matching the schema type) returns:

{"error": "Invalid arguments for create_clips: exportResolution: Invalid input"}

Request: Either honor the documented schema values, or update the schema to reflect the actual 720-only constraint so API consumers don't waste calls discovering this at runtime.

Issue 2 — No way to apply a saved Brand/Studio template via API

In Studio, selecting a "Brand template" (e.g. our "Main Template") applies a full bundle of settings in one click: resolution, orientation, caption style, language, genre defaults, etc.

create_clips has no templateId / presetId / studioPresetId field. The closest equivalent is passing a Studio template ID into captionsPreset, but that only applies the caption style — not resolution, orientation, or other template-level settings. This forces API callers to manually re-specify every individual field and still can't reach the resolutions a template would otherwise produce (per Issue 1).

Request: Add a templateId (or similar) parameter to create_clips that applies a saved Brand/Studio template's full settings, equivalent to selecting it in the Studio UI's "Brand templates" picker.

Issue 3 — add_captions can't re-process Reap's own generated clips

add_captions accepts a resolution parameter (720/1080/1440/2160) and could in theory serve as an upscale path for clips already generated at 720p. However, it only accepts an original YouTube sourceUrl or a freshly-uploaded video — passing a Reap-generated clip's own S3 download URL (reap-video-main-bkt-prod.s3-accelerate.amazonaws.com/...) fails:

{"error": "Unable to process video from reap-video-main-bkt-prod.s3-accelerate.amazonaws.co."}

Request: Allow add_captions (or a dedicated re-export endpoint) to accept Reap's own generated-clip URLs, so API users can request a higher-resolution re-render of an already-generated clip without re-running the full create_clips job from the source video.

Combined impact

Together, these three gaps mean 1080p output (or any resolution above 720p) is currently unreachable through the API for any workflow — whether starting fresh or re-processing an existing clip — even though 1080p is the default in our saved Studio template and trivially available through the Studio UI. The only current workaround is to manually reproduce the clip generation in the Studio UI by hand, which defeats the purpose of automating via the API/MCP tools.