Skip to main content
Glama

import_media_from_url

Import a publicly reachable image, video, or audio URL into Sequencer workspace media and return a mediaId. Use this when a file is already hosted at an HTTP(S) URL. Local disk paths such as C:/... are not reachable by the MCP server; use upload_media_base64 or the REST /v1/upload endpoint for local files.

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

Input Schema

NameRequiredDescriptionDefault
fileNameNoOptional file name. If omitted, derived from the URL.
folderIdNoOptional destination folder ID
mimeTypeNoOptional MIME type. If omitted, inferred from the file name or HTTP content-type.
sourceUrlYesPublicly reachable HTTP(S) URL to import
workspaceIdYesThe workspace ID
presentationNoUse timeline when the import is internal production media for an edit and should not create a standalone chat preview.standalone
idempotencyKeyNoStable upload/import key. Repeating the same bytes returns the original media without overwriting edits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / idempotencyKey
      Added value: +{
      +  "description": "Stable upload/import key. Repeating the same bytes returns the original media without overwriting edits.",
      +  "maxLength": 200,
      +  "minLength": 1,
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; it does disclose the return value (mediaId) and the server-side reachability constraint on sourceUrl, which are genuinely useful beyond the schema. However, it says nothing about size or duration limits, authentication/scope requirements, failure modes for non-media or 404 URLs, or whether the import is asynchronous (the sibling get_media_statuses hints at async processing). Those omissions matter for a network-facing import tool with zero annotation coverage.

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?

Three sentences, each doing distinct work: what it does and returns, when to use it, and when not to plus alternatives. The primary capability is front-loaded and there is no filler or repetition of schema text.

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 seven-parameter import tool with a fully documented schema, the definition covers purpose, preconditions, return value, and the key sibling routing. It falls short only on operational context such as size limits and whether the returned mediaId is immediately usable or requires polling status, which would matter given the surrounding media/status tools.

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 all seven parameters, including the presentation enum and idempotencyKey semantics, are already documented in structured form; the baseline is therefore 3. The description only reinforces sourceUrl reachability, adding no format, default, or interaction details beyond what the schema states.

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?

The description names a specific verb and resource ('Import a publicly reachable image, video, or audio URL into Sequencer workspace media') and states the return value ('return a mediaId'). It also implicitly distinguishes itself from upload_media_base64, which is named later in the text, so an agent can tell the two apart 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?

It gives an explicit positive condition ('Use this when a file is already hosted at an HTTP(S) URL') and an explicit negative case with the reason ('Local disk paths such as C:/... are not reachable by the MCP server'). It names the two alternatives for that case, upload_media_base64 and the REST /v1/upload endpoint, so routing is unambiguous.

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.