video_analyze or video_segment not in Sume tools_list? Dev host only
Sume's docs list video_analyze and video_segment as dev-only, shown only when a flag is on. On mcp.sume.com use video_inspect for what is in a clip.

On production, video_analyze and video_segment are not in Sume's tools_list. Sume's docs list them as dev-only: they appear on the development host only when a feature flag is on. For a production question like 'what happens in this clip', call video_inspect instead.
What the docs say
The source is the dev-only note on Sume's tools and gates page. Customer configs must use https://mcp.sume.com/mcp anyway, so a tutorial that uses these names is describing an environment you cannot reach.
| Item | Detail |
|---|---|
| Where | mcp.dev.sume.com and api.dev.sume.com, never production |
| Appears when | The videoUnderstand feature is enabled on that environment |
| Gates | Both need idempotency_key and max_spend_usd |
| Replaces video_inspect? | No; video_inspect stays the lightweight probe and stills tool |
What to use in production
The docs name video_inspect as the default for 'what is this clip'. It is read-only and also the tool to use for scene breakdowns, so start there. For exact frames, the docs point to video_frames_create. To cut a range out of one clip they point to video_trim.
If a client's tool list shows a name that is not on the production inventory, trust the live list: tools_list tells you what the current session can call, and tools_schema gives one tool's contract.
- Related retirement: the docs say the older
video-analyses_*tools are delisted on dev andvideo-analyses_createanswers 410video_analysis_retiredthere, while production still lists them until a later change. Do not build new work on them;video_inspectis the supported route. - Do not hard-code a dev-only tool name in a production agent prompt.
- Check
tools_listafter you connect and before you write the prompt. - A name absent from
tools_listis not callable; do not guess an alias.
The tradeoff
Dev-only tools exist so Sume can test deeper video understanding before it ships. The price for you is that a doc or example from a dev context may name tools that production will refuse. The safe habit is to treat the production tool list as the source of truth and keep the dev URL out of customer configs. If you do need a dev-only tool, ask Sume; the docs describe it as part of development testing, not as a feature you can switch on from your side, and they give no date for a production release.
Sources
Related posts
More in Developers
- video_url on Sume video: only Omni edit, Genjutsu and Recast take it
On the Sume video API, video_url is a source clip, taken by gemini-omni-flash-1.1 (edit), higgsfield-genjutsu and h3-max-recast. Others use reference_video_u...
- Voice one script in six languages: Sume TTS loop and 409 guard
MAI-Voice-2.1 sells one voice across 23 languages. On Sume, set language per line, handle the 409 voice-language guard and price a six-language batch.
- Voiceover for shorts: one sentence per shot using TTS sentence slices
Ask TTS for timestamps.words and sentence segmentation and Sume returns gapless per-sentence slices, so each shot in a short gets its own audio file.
- VoltAgent MCP 30000 ms default timeout vs Sume jobs_wait
VoltAgent's MCP timeout defaults to 30000 ms; Sume's jobs_wait holds 50 to 55 seconds. Raise it past 55000 and re-wait on wait_slice_expired.
Written by Sume