VideoVector

View saved version →

---
name: analyze
description: Use VideoVector to summarize videos, extract details, find moments, and answer questions about attached, linked, or saved media.
---

## Choose the tool

Use the five tools below. Every extraction returns segment and whole-media fields together; filtering happens afterward on those results.

- **`analyze`: extract segment and whole-media information together.** Send new attachments or media links with an extraction request directly here. For existing media, analyze again only when the needed information was not extracted.
- **`get_analysis`: load results or follow processing.** For general Q&A, load the relevant extraction into context if absent, then answer from it. Use the full JSON or paginated results when previews are insufficient; do not search merely to answer an ordinary follow-up.
- **`search`: retrieve matches from large processed collections.** Use when the extracted results for an index or set of videos cannot fit in context. Supply an explicit scope; continue result pages with `search_id` and cursor. It does not extract missing information.
- **`browse`: locate saved resources.** Find videos, indexes, analyses, imports, or prompts; then use the returned record with the appropriate tool. Browsing does not inspect video content.
- **`import_media`: transfer only.** Use when the user wants upload, copy, or import help without an extraction query, or explicitly requests no analysis. If they supply media and ask what it contains, use `analyze` directly.

`analyze` automatically saves generated extraction prompts and returns `scope.prompt_id` once available. Retain it internally and reuse it for the same extraction on other media. No separate prompt-saving step is needed.

- Forward attachments through root `files`, preserving host descriptors. A hidden download URL does not mean handoff is unavailable: attempt native forwarding. Never fabricate URLs or substitute filesystem paths. If handoff fails, explain the observed issue and request reattachment; do not require public hosting. Media URLs use `source.urls`; local stdio uploads use `source.file_paths`.

## Expand the request

The `instruction` generates the extraction JSON schema. Explicitly describe fields, visual/audio evidence, and context. Every generated prompt contains segment and whole-media fields. Processing returns all extracted data; apply selection criteria afterward in context or through search. Add relevant details the user omitted while preserving their scope and limits. Ask only when needed to proceed.

User query → expanded instruction:

- “Summarize this lecture” → “Extract main topics, definitions, important equations with plain-language explanations, worked examples, and study takeaways.”
- “Find clips for social” → “Find self-contained highlights with clear hooks. Extract title, quote, context, and why each works as a clip. Preserve the speaker's meaning.”
- “Analyze this product demo” → “Identify the product, demonstrated features, actions, and observable outcomes; distinguish demonstrations from spoken claims.”
- “Extract the action items” → “Extract decisions, actions, owners, stated deadlines, and unresolved questions. Mark missing owners or deadlines as unspecified.”
- “Help me understand this explanation” → “Extract the central idea, prerequisite concepts, reasoning steps, and examples; explain unfamiliar terms simply.”
- “Tell me what happens” → “Describe the main events in order, visible actions, people or objects involved, and relevant speech. Do not guess unclear details.”
- “Take a look at this” → “Describe the main subject, what happens, and notable visual or spoken details in a brief overview.”
- “Select social-ready scenes from this clip” → “Extract scene hooks, context, caption ideas, and editing needs for each scene, plus whole-video themes.” Select suitable scenes from the returned data.
- “Which clips contain a serious event?” → “Assess each clip for serious incidents, such as accidents or emergenc

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.