oriiion

Import Media From URL

import_media_from_url

Copy a video or image from a public http(s) link into the user's oriiion account (server-side, up to 200MB video / 25MB image, 5 minute limit) and get a mediaId + permanent URL. Google Drive and Dropbox share links work when shared as 'Anyone with the link'. Links to private networks, localhost or cloud metadata addresses are refused. Accepted: video/mp4, video/quicktime, video/webm, image/jpeg, image/png, image/webp, image/gif (decided by the file's bytes). Output: { mediaId, status: 'ready', url, kind, contentType, sizeBytes, filename }.

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

Input Schema

Name	Required	Description	Default
`url`	Yes	Public http(s) URL of the video or image file
`filename`	No	Optional filename to store it under

Output Schema

Name	Required	Description
`url`	Yes	Permanent public URL of the stored file
`kind`	Yes
`status`	Yes
`mediaId`	Yes	Opaque id (med_…) — pass it to create_post_from_video
`filename`	Yes
`sizeBytes`	Yes	Stored size in bytes
`contentType`	Yes	Content type detected from the stored bytes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnly=false, openWorld=true, idempotent=false, destructive=false) by disclosing the 200MB/25MB caps, the 5-minute limit, SSRF-style blocking of private/localhost/metadata targets, and byte-level content-type sniffing rather than trusting the extension. Those are exactly the operational traits an agent cannot infer from structured fields.

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

Conciseness4/5

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

Front-loads the core action and constraints in a dense but readable run of sentences, with no filler. The trailing 'Output: {...}' enumeration duplicates the existing output schema and is the one part that does not earn its space.

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?

Covers action, limits, accepted content types, refusal conditions, share-link nuances, and return shape — for a 2-parameter network-import tool there is nothing material an agent would still need to ask.

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 100%, so the baseline is 3, but the description adds real meaning: it defines what counts as a usable 'url' (public, http/https, resolvable share link) and ties the size/type limits to that parameter. The optional 'filename' parameter is never mentioned, which keeps it below a 5.

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?

States a specific verb and resource ('Copy a video or image from a public http(s) link into the user's account') plus the key scope qualifier: server-side import. That scope distinguishes it from the upload-link siblings (create_media_upload_url, create_upload_link, finalize_media_upload) without needing to name them.

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?

Gives clear applicability context: public http(s) links, Google Drive/Dropbox shares set to 'Anyone with the link', and explicit refusals for private networks, localhost and metadata addresses. It never names an alternative tool or says when to pick an upload flow instead, so it stops short of a 5.

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

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