Skip to main content
Glama

Upload to Sirv from URL

sirv_cdn_upload_from_url
Destructive

Copy a file from a public URL into your connected Sirv account, choosing a folder and filename or full target path. Publishes AI results to Sirv and returns the file's URL and path.

Instructions

Copy a file from a public URL into the connected Sirv account. Give folder (default /ai-tools) and filename, or the full target_path. A file already at that path is overwritten.

Use it to publish an AI result on Sirv. To keep it in the Studio library instead, use sirv_import_asset_from_url.

Returns the Sirv URL and path of the file.

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": {
      "image_url": "<image_url>"
    },
    "name": "sirv_cdn_upload_from_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoWorkspace id from sirv_list_organizations. Default: the workspace you signed in to
folderNoDestination folder in Sirv. Default: /ai-tools
filenameNoFile name in Sirv, with its extension. Default: the name in the URL
image_urlYesPublic URL of the file to copy into Sirv
target_pathNoFull destination path, such as /products/boot.jpg. Use it in place of folder and filename

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • changedInput schema / properties / filename / description
      Previous value: -"Filename in Sirv"New value: +"File name in Sirv, with its extension. Default: the name in the URL"
    • changedInput schema / properties / folder / description
      Previous value: -"Destination folder (default /ai-tools)"New value: +"Destination folder in Sirv. Default: /ai-tools"
    • changedInput schema / properties / image_url / description
      Previous value: -"Public URL of the file to upload"New value: +"Public URL of the file to copy into Sirv"
    • changedInput schema / properties / orgId / description
      Previous value: -"Organization ID (uses default org if omitted)"New value: +"Workspace id from sirv_list_organizations. Default: the workspace you signed in to"
    • addedInput schema / properties / orgId / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
    • changedInput schema / properties / target_path / description
      Previous value: -"Full destination path; replaces folder and filename"New value: +"Full destination path, such as /products/boot.jpg. Use it in place of folder and filename"
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description reinforces this with 'A file already at that path is overwritten', which is the key risk an agent needs. It also discloses the return shape and that the operation is free. It does not address source-URL constraints (size, availability) or what happens on partial failure, which is why it stops short of a 5.

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?

The core action and overwrite risk are front-loaded, and the alternative-tool routing is its own paragraph. The closing 'Credits: free.' line is minor but not load-bearing for tool selection.

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?

With no output schema, the description usefully states that it returns the Sirv URL and path, and it covers the overwrite side effect plus sibling routing. Remaining gaps (size limits, failure behavior on an unreachable source URL) are modest for a simple copy operation.

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 every parameter already carries its own description, including the folder default and the 'use in place of folder and filename' note for target_path. The description restates those defaults rather than adding new meaning, so the baseline of 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 and resource: copy a file from a public URL into the connected Sirv account. It also names the sibling it is not (sirv_import_asset_from_url), so the agent can separate 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 an explicit use case ('publish an AI result on Sirv') and an explicit alternative with the condition that selects it ('To keep it in the Studio library instead, use sirv_import_asset_from_url'). Nothing about when to pick this tool 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.