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.

4 min readSume
All posts

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.

Dev-only video tools (Sume docs, read 2026-10-06)
ItemDetail
Wheremcp.dev.sume.com and api.dev.sume.com, never production
Appears whenThe videoUnderstand feature is enabled on that environment
GatesBoth 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 and video-analyses_create answers 410 video_analysis_retired there, while production still lists them until a later change. Do not build new work on them; video_inspect is the supported route.
  • Do not hard-code a dev-only tool name in a production agent prompt.
  • Check tools_list after you connect and before you write the prompt.
  • A name absent from tools_list is 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

All Developers posts

Written by Sume