analyze_video_start
Launch Gemini video analysis as a background job and get a job_id. Poll for results after completion.
Instructions
Launch Gemini video analysis as a background job. Returns in <1s with a job_id.
This is the default for both single-video and multi-video requests.
For multiple videos, fire this tool N times back-to-back (each call
returns in <1s with its own job_id) — the analyses run concurrently
in background threads, so wall-clock time is bounded by the slowest
single video (~3-10 min), NOT N × per-video time. Then poll
analyze_video_result(job_id) for each job_id.
Use analyze_videos_batch_start ONLY when the user explicitly says
"no rush", "overnight", or for scheduled / cron digests where minutes-
to-hours latency is acceptable in exchange for 50% cost savings.
Podcast-length videos take Gemini 3-15 min to analyze, which exceeds typical
MCP host request timeouts (Claude Desktop, Claude Code, OpenClaw all cap
individual tool calls at ~60s). This tool spawns a background thread and
returns immediately; poll analyze_video_result(job_id) to get the
finished analysis.
Does NOT update discovery state. Caller is responsible for calling discover_new_videos (which manages state) beforehand.
Args:
video_url: Full YouTube URL (https://www.youtube.com/watch?v=...)
max_retries: How many Gemini retries on empty/short output (default 3)
prompt: Optional override for the analysis prompt. If None, the
default ships with an investment-podcast persona — set
$VIDEO_ANALYSIS_PROMPT_PATH to change the host-wide default,
or pass prompt here for a one-off override (e.g. "summarize
this technical talk in 5 bullets").
Returns: { job_id, video_url, status: "pending" }
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| video_url | Yes | ||
| max_retries | No | ||
| prompt | No |