Render a Short over MCP: timeline_create, jobs_wait, timeline_get

Three hosted MCP tool calls turn a Timeline document into a vertical Short: create with an idempotency_key, wait on the job, then fetch the result.

4 min readSume
All posts

On the hosted MCP server, rendering a Short is three tool calls: timeline_create submits the Timeline document, jobs_wait waits for the job, and timeline_get reads the result, which is GET /v1/jobs/:id/result. The write needs an idempotency_key, and under OAuth the mcp:write scope. Read from the Sume docs on 2026-10-06.

What does each call take?

Hosted MCP flow for a Timeline render (read 2026-10-06)
StepToolNotes
1timeline_createSame document as the REST route; requires idempotency_key
2jobs_waitWaits on the job; call again if it is still running
3timeline_getReturns video_url, duration_seconds, billable_minutes and warnings

What should the agent put in the document?

Keep it declarative: audio.duration_seconds at 180 or less for a Short, video[] slots with increasing starts, and the default 1080x1920 frame. Ffmpeg fields such as codec or filtergraph are refused, so do not let an agent invent them. Media must already be media.sume.com URLs from a prior import.

Why loop on jobs_wait?

A single jobs_wait call may return before a long render finishes, so call it again. Do not resubmit with a new key while waiting, since that would start and bill a second render.

Sources

Related posts

More in Integrations

All Integrations posts

Written by Sume