Skip to main content
Glama

Server Details

Understand your videos with Reka AI — search, ask questions, and extract insights.

If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 17 tools

Disambiguation5/5

Each tool targets a distinct purpose: video lifecycle management (upload, get, list, update, delete), group management, content retrieval (transcript, captions, scenes), search, QA, object detection, and metadata exploration. The boundaries are clear, and cross-references in descriptions guide when to use each tool.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., upload_video, get_transcript, search_videos). The verbs are imperative and descriptive, making the naming uniform and predictable across the entire set.

Tool Count4/5

With 17 tools, the count is slightly above the ideal 3-15 range, but the breadth of features (video upload, indexing, multiple analysis modes, grouping) justifies the number. The tools are well-scoped with no redundancy, though a leaner design might consolidate some retrieval functions.

Completeness5/5

The tool surface covers the full video lifecycle: upload, index, retrieve, search, analyze, update, delete, and group management. Feature catalog and status checking fill any informational gaps, and the workflow guidance (search to find timestamps, then ask or segment) closes potential dead ends.

Available Tools

17 tools
ask_videoA
Read-only
Inspect

Ask a question about one or more videos with visual analysis. Most effective on focused time ranges — use start/end to specify the segment to analyze.

BEFORE calling this tool, read the reka://docs/guide resource for recommended workflows. In most cases, you should first:

  • search_videos to find WHEN something happens, then pass those timestamps here as start/end

  • segment_video to detect and locate specific objects

  • get_transcript to read what was said

For single-video questions, pass video_id with start/end. For cross-video questions, pass videos — a list of video references with start/end each.

For follow-up questions, pass conversation_id from the previous response. You can add start/end to drill into a specific moment while keeping the conversation context.

Requires qa_only or full pipeline.

Inputs: question (required), end, start, videos, +3 more. Returns: result

create_groupAInspect

Create a new video group. Groups organize videos into collections. Returns the new group's ID and name.

Inputs: name (required), rationale. Returns: result

delete_groupA
DestructiveIdempotent
Inspect

Delete a video group. Videos in the group are not deleted — they are simply removed from the group.

Inputs: group_id (required), rationale. Returns: result

delete_videoA
DestructiveIdempotent
Inspect

Permanently delete a video and all its indexed data (transcript, captions, embeddings, etc.). This cannot be undone.

Inputs: video_id (required), rationale. Returns: result

get_captionsA
Read-onlyIdempotent
Inspect

Get AI-generated visual descriptions of what happens on screen. Use this to understand the visual content without watching — each caption describes a short segment with timestamps.

Use start/end to narrow results.

Requires the captions feature (qa_only or full pipeline).

Inputs: video_id (required), end, start, rationale, +1 more. Returns: result

get_feature_catalogA
Read-onlyIdempotent
Inspect

List available video analysis features with their dependencies and descriptions. Use this to understand what features exist and what pipelines to use with index_video.

Inputs: rationale. Returns: result

get_scenesA
Read-onlyIdempotent
Inspect

Get detected scene boundaries with start/end timestamps. Use this to understand the video's structure, then pass scene timestamps as start/end to:

  • ask_video for per-scene contextual analysis

  • segment_video to detect specific objects per scene (scenes typically fit in segment_video's 15s max range)

Requires transcript indexed with scene detection (on by default; skipped only if index_video was called with scene_detection=False).

Inputs: video_id (required), rationale, max_results. Returns: result

get_transcriptA
Read-onlyIdempotent
Inspect

Get the spoken words in a video. Use this instead of ask_video when you need to read what was said — it returns the actual text, not a summary.

Use start/end to narrow results for long videos.

Requires the transcript feature to be indexed.

Inputs: video_id (required), end, start, format, +3 more. Returns: result

get_videoA
Read-onlyIdempotent
Inspect

Get detailed information about a video including upload status, metadata (duration, resolution, fps), and per-feature indexing status. Use this to check if upload or indexing is complete. The 'url' field is a short-lived HTTPS presigned URL (expires within hours) — fetch immediately and do not store; call get_video again for a fresh URL when needed.

Inputs: video_id (required), rationale. Returns: result

index_videoA
Idempotent
Inspect

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.

Inputs: video_id (required), pipeline, rationale, scene_detection. Returns: result

list_groupsA
Read-onlyIdempotent
Inspect

List all video groups. Use list_videos with a group_id to see videos in a specific group.

Inputs: rationale. Returns: result

list_videosA
Read-onlyIdempotent
Inspect

List all videos in your account, or filter to a specific group by passing group_id. Shows upload status and which features have been indexed for each video. Each video's 'url' is a short-lived HTTPS presigned URL (expires within hours) — fetch immediately and do not store; call list_videos or get_video again for a fresh URL when needed.

Inputs: group_id, rationale. Returns: result

search_videosA
Read-onlyIdempotent
Inspect

Find WHEN and WHERE something happens across your videos. Returns timestamped results ranked by relevance — use these timestamps as start/end in ask_video for focused analysis.

This is the recommended first step for most questions. Instead of asking ask_video about the entire video, search first to narrow down the relevant moments.

Each result's 'video_url' is a short-lived HTTPS presigned URL (expires within hours) — fetch immediately and do not store; call search_videos or get_video again for a fresh URL when needed.

Requires search_only or full pipeline.

Inputs: query (required), group_id, rationale, video_ids, +1 more. Returns: result

segment_videoA
Read-onlyIdempotent
Inspect

Detect objects in a video segment using text prompts. Describe what to look for and get per-frame detections with bounding boxes and confidence scores.

Prompt tips:

  • Use broad, visual categories: 'animal', 'vehicle', 'person', 'text on screen'

  • Specific labels ('rabbit', 'Toyota') are less reliable — the detector matches visual patterns, not semantic concepts

  • Best for confirming whether a category of object appears in a time window, not for precise identification

How to pick a time range:

  • Use search_videos to find WHEN something appears, then pass those timestamps here

  • Use get_scenes to scan systematically — call segment_video once per scene (scenes typically fit in the 15s window)

  • Or pass any range you already know

Maximum range is 15 seconds per call; for longer spans, make multiple calls with consecutive windows.

Does NOT require any feature indexing — works on any uploaded video.

Inputs: start (required), prompts (required), video_id (required), end, +2 more. Returns: result

summarize_videoA
Read-onlyIdempotent
Inspect

Start here. Get a compact overview of a video: metadata, which features are indexed, a transcript preview, and scene count. Use this to decide which tools to call next — then use segment_video to detect specific objects in time ranges of interest.

Inputs: video_id (required), rationale. Returns: result

update_videoA
Idempotent
Inspect

Update a video's display name, title, description, or move it to a different group. At least one field must be provided. To remove a video from its group, pass group_id as null.

Inputs: video_id (required), name, title, group_id, +3 more. Returns: result

upload_videoAInspect

Upload a video from a URL. Returns a video_id. Local file paths are not accepted; upload files outside the MCP server and pass a reachable video_url. The upload runs asynchronously — poll get_video until status is 'uploaded', then call index_video to enable search and analysis.

Inputs: video_url (required), name, group_id, rationale, +1 more. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources