Analyze the given video and answer the user's question (or summarize it if no question was asked). Always cite timestamps (M:SS) in your answer.

Route A — video-analyzer MCP tools available (preferred)

If the video-analyzer MCP server is connected in this session, call its tools directly — do not use the CLI:

General question or no question → analyze_video (detail "standard")
"What happens at X:XX" / a specific moment → analyze_moment (time range) or get_frame_at
Question answerable from speech alone → get_transcript (fast, no download)
Title / duration / views / comments only → get_metadata (no download)
Motion or fast UI changes → get_frame_burst

For subsecond motion, use fractional bounds (for example, 0:01.1 to 0:01.3). FFmpeg burst extraction returns up to the requested count of real source frames; it does not duplicate frames when the requested rate exceeds the source rate. Preserve fractional timestamps when supplied. Browser fallback uses fractional seek targets, but those are not measured source-frame presentation timestamps.

Dense UI capture (terminal, dashboard, IDE, spreadsheet — the meaning is in small text): pass maxWidth on any of these tools. Emitted frames are capped at 800 px wide by default, which turns a 1920×1080 screencast into 800×450 and drops a 15 px UI font below what a vision model can read. maxWidth: 0 keeps the source resolution; a value like 1568 is the middle ground. Native frames cost several times more context, so raise it for the close read, not for the overview.