Simpler.Asia

studio.import_asset_from_url

Copy a video, audio or image file from a public http(s) link into a studio project's media (up to 2 GB, within the 20 GB quota). Returns {asset_id, media_type, probe}, the same as studio.finish_asset_upload. The link is only downloaded; nothing is posted to it. Refuses: localhost, private, link-local or cloud-metadata addresses, or a redirect to one (SIMPLER_STUDIO_IMPORT_URL_REFUSED): give a public link; a link that fails or answers an error (SIMPLER_STUDIO_IMPORT_FETCH_FAILED): check it downloads without signing in; a file over the limit or the quota (SIMPLER_STUDIO_UPLOAD_TOO_LARGE / SIMPLER_STUDIO_UPLOAD_QUOTA): GET /api/studio/uploads lists your stored files, then delete unused ones; a page or unsupported format (SIMPLER_STUDIO_UPLOAD_TYPE_UNSUPPORTED): link to the media file itself; a source that stalls (SIMPLER_STUDIO_IMPORT_TIMEOUT): try again or upload with studio.begin_asset_upload. Free.

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": {
      "project_id": "<project_id>",
      "url": "<url>"
    },
    "name": "studio.import_asset_from_url"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	A public http(s) link that downloads the media file itself.
`project_id`	Yes	The studio project (vp_...) to add the file to.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only say readOnlyHint=false; the description supplies everything else: 2 GB per-file cap, 20 GB quota, download-only (nothing posted to the link), SSRF guards against localhost/private/link-local/cloud-metadata and redirects, and a concrete recovery path per error code.

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-loaded with the action, limits, and return shape before the failure catalogue. The error-code enumeration is long but each item pairs a code with an action, so it stays actionable rather than padding.

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?

No output schema exists, yet the description declares the return shape ({asset_id, media_type, probe}), the size and quota ceilings, the security posture, and every likely failure mode with a next step. Nothing material is missing for correct invocation.

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 semantics: the link must be anonymously fetchable ('check it downloads without signing in'), must resolve to the media file itself, and redirects to private addresses are rejected. The project_id argument gets no extra meaning beyond the schema.

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, audio or image file from a public http(s) link into a studio project's media') and even ties its output to a sibling ('the same as studio.finish_asset_upload'), so an agent can distinguish the URL-import path from the upload-session path without opening the schema.

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?

It gives explicit refusal conditions and remediation for each, and names an alternative (studio.begin_asset_upload) when the source stalls. What it doesn't state up front is the positive selection rule versus begin/finish_asset_upload for files you already hold locally.

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

All Simpler.Asia 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?