Reka

index_video

Idempotent

Index a video for search, QA, or full analysis. Processes the video through a pipeline of AI features. Typically takes 3-7 minutes; longer for long videos or the 'full' pipeline. Times out after 10 minutes by default.

Pipelines:

search_only: transcription + captions + embeddings (enables search_videos)
qa_only: transcription + captions (enables ask_video)
full: transcription + captions + embeddings (enables all tools)

Scene detection is enabled by default and produces scene boundaries for get_scenes. Pass scene_detection=False to skip it.

Prerequisites: if using video_id, the video must be in 'uploaded' status. Use get_video to check status before calling this tool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "video_id": "<video_id>"
    },
    "name": "index_video"
  }
}

Input Schema

Name	Required	Default
`pipeline`	No	search_only
`video_id`	Yes
`rationale`	No
`scene_detection`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 14, 2026

addedInput schema / properties / scene_detection

Added value: +{
+  "default": true,
+  "title": "Scene Detection",
+  "type": "boolean"
+}

Changed7 schema fields changedMay 11, 2026

removedInput schema / properties / file_path

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "File Path"
-}

removedInput schema / properties / video_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / video_id / default
```
Removed value: -null
```
addedInput schema / properties / video_id / type
```
Added value: +"string"
```
addedInput schema / required
```
Added value: +[
+  "video_id"
+]
```

changedInput schema / title

Previous value: -"index_videoArguments"New value: +"index_video_hostedArguments"

changedOutput schema / title

Previous value: -"index_videoOutput"New value: +"index_video_hostedOutput"

First observedMay 8, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds substantial behavioral context beyond annotations: processing times (3-7 minutes), timeout (10 minutes), default scene detection, and the prerequisite that the video must be in 'uploaded' status. It does not contradict the idempotentHint annotation and enriches the operability knowledge.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the primary purpose, followed by essential timing, pipeline breakdown, scene detection note, and prerequisite. It uses clear headers for pipelines and prerequisites, and every sentence adds operational value without fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (multiple pipelines, 4 parameters, defaults, and an output schema), the description covers prerequisites, timeout, pipeline effects, and scene detection. The existence of an output schema means return values need not be described. The description is complete enough for an agent to correctly invoke and handle the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description fully compensates by explaining the semantics of the pipeline parameter (search_only/qa_only/full), scene_detection (default true, skip with false), and the important 'uploaded' status requirement for video_id. Only the rationale parameter is left unexplained, but that is ancillary.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Index a video') and the resource, with specific purpose ('for search, QA, or full analysis'). It distinguishes from siblings like upload_video, segment_video, and search_videos by clarifying that this tool builds the index that enables those other tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use specific pipeline types and includes a prerequisite instruction to check video status via get_video before calling. However, it doesn't explicitly state when NOT to use this tool (e.g., if only captions are needed) or mention alternative tools beyond the pipeline a enable relation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Reka tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?