Kuro

Import a public video link

import_video_url

Idempotent

Import one public YouTube, Facebook or TikTok video (up to 10 minutes and 250 MB) into the Library. Returns an asynchronous import: poll get_video_import until ready, then use its upload_id. Import costs no credits and uses storage quota. analyze_after_import runs the app analyst for 5 credits; leave false to analyze with your own model using measure_video and save_video_analysis. Private videos, playlists and live streams are unsupported.

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": {
      "url": "<url>"
    },
    "name": "import_video_url"
  }
}

Input Schema

Name	Required	Default
`url`	Yes
`product`	No	kuro
`analyze_after_import`	No

Output Schema

Name	Required	Description	Default
`import`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 15, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses asynchronous return semantics, the polling tool, credit cost (zero for import, 5 for analyze_after_import), storage quota consumption, and size/duration caps. Annotations already flag openWorld and idempotent, and nothing here contradicts them.

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?

Four dense sentences, each carrying distinct operational information, with the core action and constraints front-loaded before the cost and follow-up guidance. No filler.

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?

For an async import tool with an output schema available, the description supplies everything the agent needs to call it and continue the workflow: constraints, async contract, cost model, and the completion tool to poll. Only the trivial single-value product enum is unaddressed.

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

Parameters4/5

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

Schema coverage is 0%, so the description carries the burden and does well for two of three params: url is bounded by platform/limit constraints, and analyze_after_import is explained with its exact cost and the false-branch alternative. The product parameter (enum 'kuro', default 'kuro') is never mentioned, leaving a small gap.

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?

Specific verb (import), specific resource (one public video), named sources (YouTube, Facebook, TikTok), and hard limits (10 minutes, 250 MB). An agent can immediately distinguish this from generic ingestion paths like import_media or create_upload.

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?

Explicitly covers when to use (public video links within limits), when not to (private videos, playlists, live streams unsupported), and the follow-up path (poll get_video_import, then use upload_id). It also names the decision point between the built-in analyst and a self-driven analyze path via measure_video and save_video_analysis.

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

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