Skip to main content
Glama

Import Asset from URL

sirv_import_asset_from_url

Download a file from a public URL and add it to the Studio library as a new asset, so AI results or outside images stay available for reuse.

Instructions

Download a file from a public URL and add it to the Studio library as a new asset.

Use it to keep an AI result or an outside image in the library. Do not use it to put the file in the connected Sirv account: use sirv_cdn_upload_from_url.

Inputs: url and filename (with its extension, such as boot.jpg) are required. fileSize in bytes is optional, and orgId picks another workspace.

A source that fails returns an error code: IMPORT_URL_BLOCKED for a private, non-HTTP or credentialled URL, IMPORT_UNSUPPORTED_TYPE for a file that is not an image or media, and IMPORT_SOURCE_UNAVAILABLE when the source answers with an error. Returns the new asset with its id and URL.

Credits: 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": {
      "url": "<url>",
      "filename": "<filename>"
    },
    "name": "sirv_import_asset_from_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic HTTP or HTTPS URL of the file to import
orgIdNoWorkspace id from sirv_list_organizations. Default: the workspace you signed in to
fileSizeNoFile size in bytes, when you know it
filenameYesFile name for the new asset, with its extension, such as boot.jpg

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by naming three concrete failure modes and their trigger conditions (blocked/private/credentialled URL, unsupported type, unavailable source) and by disclosing the credit cost. It also states what a successful call yields, the new asset with id and URL, which annotations cannot express.

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?

Purpose first, then the sibling exclusion, then inputs, error codes and cost, each in its own short block. No sentence is redundant and the highest-value routing information is front-loaded.

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?

Although there is no output schema, the description names the return payload (asset with id and URL) and enumerates the error codes, leaving nothing material an agent needs before calling it. For a four-parameter import with annotations covering the safety profile, the coverage is complete.

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 coverage is 100%, so all four parameters are already documented with formats and defaults. The description restates the required/optional split and the extension convention but adds no semantics the schema lacks, including nothing new about fileSize or orgId beyond what the schema says.

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 file from a public URL and add it to the Studio library as a new asset." It also explicitly separates itself from the sibling that writes into the CDN account, so an agent can discriminate between the two 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 both a positive case ("keep an AI result or an outside image in the library") and a negative case with a named alternative ("Do not use it ... use sirv_cdn_upload_from_url"). The selection condition is explicit rather than inferred.

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