RipClip

Import video

import_video

Idempotent

Use this when the user wants to bring a long video into RipClip so it can be clipped: "clip this Twitch VOD", "turn my Kick stream into shorts", "use this podcast episode", "clip my last stream". Give url: a Kick or Twitch past broadcast (VOD), highlight or clip link, an Apple Podcasts episode, a Google Drive, Dropbox or OneDrive share link, or a direct link to a video file. Or give channel (the streamer's name) with platform "kick" or "twitch", or a channel page link such as kick.com/name: that imports the channel's newest past broadcast. rights must be true only after the user confirms they own the video or have permission to use it. request_key is any stable string; reuse it only to retry this exact import. Returns job_id at once; poll job_status, which gives the project_id when it is done. Not for: YouTube links (not supported: the user uploads the file in RipClip), a stream that is still live (import it after it ends), or cutting clips (find_clips) and posting (draft_post). Free: importing spends no Horizon Units. Next: estimate_hu, then find_clips.

Input Schema

Name	Required	Description	Default
`url`	No
`rights`	No
`channel`	No
`platform`	No
`request_key`	Yes

Output Schema

Name	Required	Description	Default
`job_id`	Yes
`status`	Yes
`status_url`	Yes
`reserved_hu`	Yes
`results_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond annotations, it explains rights confirmation requirements, idempotency expectations for request_key, immediate job_id return, polling via job_status, and that importing spends no Horizon Units. These details materially affect correct invocation behavior.

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 long but appropriately so for a five-parameter tool with multiple import modes. It is front-loaded with usage guidance and each sentence adds operational value.

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 complexity, open-world annotations, and output schema, the description covers the essential workflow: import, immediate job_id, polling job_status, and retrieving project_id. No critical invocation context is missing.

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 accepted url sources, channel/platform combinations, rights semantics, and request_key retry behavior. It adds meaning well beyond the bare parameter names.

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 states a specific action and resource: bringing a long video into RipClip so it can be clipped. It distinguishes the tool from siblings by naming exclusions like YouTube links, live streams, find_clips, and draft_post.

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

Usage Guidelines5/5

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

It gives explicit when-to-use examples, when-not-to-use cases, and alternative next steps: estimate_hu then find_clips. It also tells the agent not to use it for cutting clips or posting.

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

All RipClip 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?