Skip to main content
Glama

import_media_from_url

Download an image, audio, or video file from a public URL and save it to SkyGen S3. Returns the persistent SkyGen S3 URL. Use this when the user has already provided a URL or an attached file download link. Always prefer this over request_media_upload if you already have a URL.

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

NameRequiredDescriptionDefault
urlYesThe public URL of the media file to import.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations say readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds that it fetches external media and persists it in SkyGen S3 with a returned persistent URL, which is useful beyond annotations. It omits failure behavior for private/inaccessible URLs and any size limits, so not fully transparent.

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?

Three sentences, front-loaded with the action and result, then the usage rule and alternative. Minor redundancy with the schema's 'public URL', but no filler.

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 single-parameter import tool with annotations covering safety and no output schema, it covers purpose, return value, and routing. Only edge-case behavior (non-public URLs, error handling) is absent.

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?

Only one parameter with 100% schema coverage, and the schema already states it must be a public URL. The description adds little beyond that, so the baseline 3 applies.

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 (Download) plus the resources (image, audio, video) and destination (SkyGen S3), and gives the return value. It distinguishes itself from request_media_upload by name.

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?

Explicitly says to use it when the user has provided a URL or attached download link, and names the alternative: 'Always prefer this over request_media_upload if you already have a URL.' The selecting condition is fully spelled out.

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.

Resources