Skip to main content
Glama

Import a video from a link

import_video

Bring a video into Tuney from a public https link that returns the file itself (not a web page).

    Returns the video_id to pass to score_video, analyze_video or render_video. Videos up to
    200 MB and 10 minutes. For a local file, use get_video_upload_link instead.
    

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true and readOnlyHint=false, so the description's job is to add operational detail, and it does: hard limits of 200 MB and 10 minutes, plus the requirement that the link be public and serve the file directly. It does not say whether the import is synchronous or whether a long fetch should be polled via wait_for_task/get_task, which is the one behavioral gap for a network-bound ingestion.

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?

Two short paragraphs, front-loaded with the core action and its key constraint, followed by the return value and the sibling alternative. Every sentence carries distinct information; nothing is repeated from the annotations or schema.

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

Completeness4/5

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

For a single-parameter ingestion tool with an output schema present, the definition supplies the constraints, the alternative path, and the downstream consumers, which is close to sufficient. The remaining gap is failure/latency behavior for a large remote fetch, which an agent would want when deciding whether to wait or poll.

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% — the schema documents only a bare 'url' string — so the description carries the full burden and largely does: the URL must be https, public, and return the file itself, with size and duration ceilings implied as preconditions. It stops short of an example URL or supported formats/redirect/auth handling, leaving some ambiguity about what will be rejected.

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?

Names a specific verb and resource ('Bring a video into Tuney') and immediately constrains the source to a public https link that serves the file itself rather than a web page. The parenthetical 'not a web page' actively disambiguates from the most likely misfire, so an agent can distinguish this from get_video_upload_link without opening either schema.

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?

Gives an explicit alternative for the opposite case ('For a local file, use get_video_upload_link instead') and names the downstream tools that consume the returned video_id (score_video, analyze_video, render_video), which tells the agent where this fits in a workflow. The direct-file constraint functions as a clear when-not condition.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.