No user-submitted related servers found.
Scored across 203 tools
The surface contains many near-duplicate tools: video_info vs video_info_detailed vs video_read_metadata, video_add_text vs video_add_texts vs video_text_animated, and overlapping scene detection via video_detect_scenes, video_ai_scene_detect, and video_auto_chapters. Audio mixing also has several similar entry points such as video_mix_audio, video_duck_audio, and video_audio_bed, leaving boundaries unclear for an agent.
Names are mostly snake_case and readable, but conventions are fragmented across many domain prefixes: video_*, effect_*, glitch_*, transition_*, audio_*, still_*, hyperframes_*, shorts_*, and sound_*. The verb/noun ordering is also inconsistent, e.g. video_filter vs effect_vignette, transition_glitch vs glitch_rgb_shift, and plan/render/inspect tools mixed across domains.
At 203 tools, the server is far beyond a well-scoped surface for an agent to select from. Even a broad video-production toolkit should consolidate many of these operations into fewer parameterized or workflow-driven tools.
Coverage is very broad: editing, conversion, audio, subtitles, effects, QC, review, workflows, stills, and Hyperframes/Revideo rendering are all represented. There are some dead-end or partial paths, such as plan-only tools and features gated by GPU/Node or disabled provider adapters, but the core lifecycle is well covered.