generate_video MCP defaults to sume/auto; REST requires model
The generate_video MCP tool defaults model to sume/auto, but POST /v1/videos requires model. Same payload schema; the MCP server adds the default.
The generate_video MCP tool makes model optional and defaults it to sume/auto. The REST route POST /v1/videos still requires model, and the MCP server adds the default before the body goes out. The payload schema is otherwise the same: one contract, two transports.
Tool to route
The Sume docs map the MCP tools to REST like this.
| MCP tool | REST route |
|---|---|
generate_video | POST /v1/videos |
video-router_models | GET /v1/videos/models |
What the default gives you
sume/auto lets Sume pick the model. It resolves as a pure function of the request, so an idempotent replay gets the same route and price. Responses echo sume/auto, and Sume does not say which family ran. If a request asks for something the auto route cannot serve, it fails with 400 unsupported_capability and supported lists the accepted values. To pin a family, pass a catalog id.
One schema
A drift test in the repo compares the MCP payload schema with the REST request schema for keys and enums, so MCP cannot accept a key or value that REST rejects. There is no medias[] field on either side.
Old tool name
The tool shipped on 2026-08-04 as video-router_create. That name still resolves when called, but the tool list no longer shows it. New agents should call generate_video.
Porting an agent call to REST
If you write a REST client from an agent's tool call, add model yourself. Use sume/auto to match the agent, or a catalog id from GET /v1/videos/models to pin a family.
curl -X POST https://api.sume.com/v1/videos \
-H "Authorization: Bearer $SUME_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "sume/auto", "prompt": "A vertical product clip on a desk", "aspect_ratio": "9:16", "duration": 5}'Sources
Related posts
More in Agents
- jobs_cancel on Sume MCP: Write scope, idempotency_key, early moment
jobs_cancel is a write tool marked destructive. It needs the mcp:write scope or an API key, an idempotency_key, and a job that has not started generating.
- Sume jobs_wait with 20 ids: one unknown id fails the whole call
A batch jobs_wait takes 1 to 20 ids. One unknown or foreign-workspace id makes the full call fail, so validate ids with jobs_list or jobs_status first.
- jobs_wait returned early during a deploy: retry the same job ids
A Sume MCP jobs_wait can return before its 50 second slice when the API host is draining for a deploy. The job is fine: call jobs_wait again on the same ids.
- jobs_wait with timeout_seconds 0: a single status snapshot on Sume MCP
Sume's jobs_wait accepts timeout_seconds 0 to 600 (clamped to 55) and interval_seconds 1 to 60. A value of 0 reads the status once and returns right away.
Written by Sume