Related Servers

Multiple tool clusters have genuinely unclear boundaries: add_track/add_tracks duplicate the same operation, speed_change and set_clip_speed_qe are two dead stubs for the same unsupported feature, and get_clip_properties/get_full_clip_info/get_qe_clip_info plus set_clip_properties alongside set_clip_position/scale/rotation/opacity overlap heavily. With five frame-export tools, a half-dozen capability/connectivity checks, and dozens of similar plan_*/preview_* tools, an agent will frequently misselect despite the unusually detailed descriptions.

The dominant verb_noun snake_case pattern (get_*, set_*, create_*, delete_*, import_*, export_*) is predictable and readable, but conventions fray at the edges: scene_edit_detection sits next to detect_scene_edits for the same feature, batch operations exist as both batch_* prefixes and *_batch suffixes (batch_add_transitions vs add_markers_batch), and delete vs remove are used interchangeably for similar removals.

379 tools is nearly eight times the 'extreme' calibration threshold of 50, and the count includes roughly a dozen dead tools (undo, redo, multiple_undo, speed_change, set_clip_speed_qe, reverse_clip, nest_clips, add_text_overlay, import_edl, replace_clip_media) that exist only to return 'unavailable' errors. The count reflects exhaustive, uncurated coverage; dozens of near-synonymous get_*/inspect_*/plan_* tools could be consolidated without losing capability.

The surface covers the full lifecycle for every major Premiere resource — projects, sequences, clips, tracks, markers, effects, metadata, proxies, and export — plus source-monitor editing, MOGRT/After Effects handoffs, EDL/FCPXML interchange, and FFmpeg-based analysis. Genuine host API limitations (speed change, undo, nesting, raw-text captions) are explicitly surfaced as documented unavailable tools rather than silently missing, so agents get a clear boundary instead of guessing.