Trim an ad cutdown from an MCP client: dry run, wait, result

From an MCP client connected to Sume's hosted MCP server, a cutdown is three tool calls: video_trim with your trim as payload, jobs_wait on the job id, and jobs_result to read the new video_url. The write needs an idempotency_key, and under OAuth the mcp:write scope. Add dry_run: true to the first call to see the $0.02 estimate without submitting.

The tool names and flow are in MCP tools and gates and the trim fields in Video trim (read 2026-10-06). The payload is the same body as POST /v1/video-trim.

What does the dry run return?

With dry_run: true, the tool returns a fixed-price estimate and would_submit: false, and no job is created. Send the same arguments without dry_run to submit. If you pass max_spend_usd, the tool checks it against the fixed estimate.

{
  "idempotency_key": "bf-cutdown-15s-001",
  "dry_run": true,
  "payload": {
    "video_url": "https://media.sume.com/artifacts/artf_demo/bf-master-45s.mp4",
    "start": 0,
    "duration": 15
  }
}

How do I wait for the cut?

Call jobs_wait with the job id from the submit. A slice is 50 seconds by default and 55 at most, so on wait_slice_expired call it again with the same id, and never submit the trim again.

What do I do with the result?

Use the new video_url as a video[] source in timeline_create with source_in 0, or caption it. The source is never changed, and video_trim returns a new artf_ file each time.

• The source must already be a media.sume.com file of your workspace.
• A retry with the same idempotency_key and body should not bill a second job.
• A cut of 15 seconds from a 45-second master is one trim, so three versions are three calls.