AskEditor

Import media from URL

import_media_from_url

[write] Download a public video, image or audio file into the workspace library (video up to 400 MB, audio 100 MB), measure it, and optionally place it on the timeline. Use for a direct link to an mp4/mov/webm, jpg/png/webp/gif or mp3/wav/m4a file. A private or local address is refused. Not for a web page (use find_site_assets) or a file on your machine (use create_upload). Returns asset_id, kind, name, duration_ms, width, height, reused, and placed {handle, lane, start_ms, end_ms} when placed. Related: list_media, add_timeline_clip, create_upload. Full docs: load_skill with tools: [name].

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>"
    },
    "name": "import_media_from_url"
  }
}

Input Schema

Name	Required	Description
`url`	No	Direct http(s) link to the file itself.
`kind`	No	What it is (default read from the address).
`name`	No	Library name (default the file's).
`items`	No	Many files at once, max 40, each with this tool's fields; fields beside it are defaults.
`place`	No	Also lay it on this project's timeline.
`project_id`	Yes	The AskEditor project this acts on (from list_projects).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations only declare write/openWorld/non-idempotent/non-destructive; the description adds material behavior the annotations cannot: 400 MB video and 100 MB audio limits, refusal of private or local addresses, deduplication signalled by the "reused" return field, and the side effect of placing a clip on the timeline. It also lists the return payload since no output schema exists.

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?

A single dense paragraph with the [write] marker and the core action front-loaded, then constraints, then exclusions, then return shape. Every sentence carries distinct information; there is no filler or restatement of the title.

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 the full calling contract for a 6-parameter tool with a nested `place` object: what it accepts, what it refuses, side effects, and the return fields in lieu of an output schema. An agent has enough to call it correctly and predict the result.

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

Parameters3/5

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

Schema description coverage is 100%, so parameters are already well documented; the description only adds a light gloss on the optional placement behavior ("optionally place it on the timeline"). It never mentions the batch `items` array (max 40) or the defaulting rules for `kind`/`name`, which the schema does cover, so the description neither compensates nor detracts.

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 ("Download a public video, image or audio file into the workspace library") plus scope details: size caps, supported formats, and the optional timeline placement. It explicitly distinguishes itself from find_site_assets and create_upload, so an agent can pick it without opening a sibling 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 explicit when-to-use ("a direct link to an mp4/mov/webm, jpg/png/webp/gif or mp3/wav/m4a file") and when-not-to-use with named alternatives for both failure cases ("Not for a web page (use find_site_assets) or a file on your machine (use create_upload)"). Nothing about selection is left to inference.

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

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