1---2name: vidxp-find-video-evidence3description: Use VidXP to search indexed videos and surface inspectable evidence boards, keyframes, and clips before analysis. Trigger for requests such as "find where X appears," "when does Y happen," "what is said," "what happens," or "show me the matching clip," even when the user does not name VidXP. Favor one-pass evidence delivery and only add brief accuracy feedback; do not trigger for ingesting new media or ordinary video editing.4---56# Find video evidence with VidXP78## Workflow9101. Resolve the `vidxp` MCP tools, then call `get_workspace`. If the requested11 video is not indexed, explain that it must be indexed first.122. Submit one retrieval job. Use `search_moments` to locate moments; use13 `query_video` only when the user asks for a synthesized answer. Use14 `command.query` with `search_moments` and `command.question` with15 `query_video`. Set `command.media_id` when the user means one video.163. In that initial job, put exactly this inside `command`:17 `"evidence_delivery": {"mode": "keyframes_and_clips", "max_items": 3}`.18 This prepares the ranked board, standalone keyframes, and clips without a19 second retrieval pass. Never send `command.materialize`.204. Call `wait_job` for bounded waits. Pass its `observation_token` as21 `after_observation_token` on the next wait. When terminal, call22 `get_job_evidence` once. It returns the concise evidence index and visual23 content without the full structured job dump. Search and query may take24 time; update the user when the stage changes or about once per minute, never25 after every wait and never with an invented ETA.265. Surface the returned board, keyframes, and clips immediately. Do not call27 `get_job`, repeat the search, materialize more evidence, create another28 board, or perform a self-directed verification loop before showing the29 initial evidence.306. Stop after the first evidence delivery. Only when the user explicitly asks31 for another selection or format, use tile evidence IDs with32 `materialize_job_evidence`, or use `create_evidence_board` for a custom33 selection or `next_start_rank` continuation.3435## Actor scope3637- Actor data is available through `query_video`, not name search. It represents38 anonymous, video-scoped face clusters—not a named or cross-video identity.39- Treat its image as a representative full frame, not an exact face crop or40 proof of continuous presence. Do not claim exhaustive named appearances.41- For named-person requests, surface the best scene candidates immediately and42 label uncertain matches as candidates. Do not delay delivery while trying to43 prove identity through additional searches.4445## Output4647- Lead with evidence, not a search narrative: first embed the returned board or48 frame or provide its working resource link, then list the ready clips and49 keyframes. Use the returned `local_path` or `download_url`; never write an50 unlinked label such as “View evidence board.” Use `get_artifact_download`51 only if neither is returned.52- After the evidence, add at most a brief accuracy note. State uncertainty or53 visible mismatches without launching another search. Accuracy feedback must54 not replace or precede the evidence.55- Preserve the source job and evidence IDs. Describe scores as retrieval scores,56 and distinguish a visible appearance from a dialogue or caption mention.57- Stop waiting on success, failure, or cancellation. An empty result means no58 matching indexed evidence was found, not that the event is absent from the59 original video.