get_moment
Capture a single moment's evidence in one call: transcript slice, up to 3 frames with OCR text, and the exact time range.
Instructions
The "one remark" evidence bundle: transcript slice + up to 3 unique frames + their OCR text + the wall-clock range for [start_ms, end_ms], in a single call. This is the workhorse for triage: one call per finding gives you the quote, the screenshot, and the on-screen text. When NOT to use: broad exploration (get_transcript / get_frames) or keyword lookup (search). Examples:
get_moment(job_id="...", start_ms=83000, end_ms=97000) — full evidence for the remark at 1:23-1:37
segment seq 12 spans t0_ms=83210, t1_ms=96800 → get_moment(job_id, 83210, 96800)
pad ±2000 ms around the spoken range — narrators react to things already on screen
triage loop: for each candidate finding, exactly one get_moment call → quote + frame + OCR
user: "what was I showing when I said 'this button is broken'?" → search first, then get_moment at the hit
opening context of a meeting: get_moment(job_id, 0, 15000)
response includes the t_wall range when known → quote it in bug reports for log correlation
diarized job → speakers_in_range + speaker on each segment: who is talking in this window, at a glance
frame entries carry "path" (absolute) — copy the screenshot elsewhere with your own file tools
"was X on screen at t?" → yes iff some frame's valid_from_ms <= t < valid_to_ms — no extra calls needed
audio-only job → returns the transcript slice plus a no-frames note (that is expected)
anti-example: whole-video summary → get_transcript(format="text"), not a chain of get_moments
anti-example: need more than 3 frames of a range → get_frames(start_ms=..., end_ms=..., max_frames=6)
keep ranges under ~30 s; a 5-min "moment" dilutes the bundle and wastes tokens
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| end_ms | Yes | ||
| job_id | Yes | ||
| start_ms | Yes |