Skip to main content
Glama
Sign In
Sync MCP Server

Sync MCP Server

Official
by synchronicity-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get an asset download url

assets_get-download-url
Read-only

Get a signed download link for an asset's original media file by its ID, so you can save or download it. Use for external-URL assets to retrieve the original URL unchanged.

Instructions

Get a download link for one asset's original media file, by id. Use it when the user wants to download or save the file; use assets_get for the asset's details and media url, and assets_get-playback-metadata for frame timing. For files in sync. storage the link is signed, valid for up to 7 days and downloads under the asset's name; an asset registered from an outside URL returns that URL unchanged. Returns the URL as a plain string, or 404 when the asset does not exist, was deleted or you cannot see it. Return the URL exactly as given, query string included, and request a fresh one instead of reusing an old link.

Input Schema

NameRequiredDescriptionDefault
idYesAsset id (UUID) from assets_list or assets_get, not a generation id; for a generation's output use its outputMediaUrl from generations_get.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.2.4
    • changedInput schema / properties / id / description
      Previous value: -"Asset id from assets_list."New value: +"Asset id (UUID) from assets_list or assets_get, not a generation id; for a generation's output use its outputMediaUrl from generations_get."
  2. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Asset ID"New value: +"Asset id from assets_list."
  3. Addedv0.1.5

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld/destructive annotations: signed-link lifetime (up to 7 days), the filename behavior on download, the passthrough case for externally registered assets, and the 404 conditions including a permission-based invisibility case. It also gives operational guidance not to reuse or alter the link, which annotations could never convey.

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?

Front-loads purpose, then alternatives, then behavior, then return/usage rules – a sensible order. It is somewhat dense at four sentences, but each carries distinct operational information; 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?

With no output schema, the description covers the return value (plain string URL), the external-URL edge case, and the 404 failure modes, plus a caution against link reuse. Nothing needed to call this single-parameter tool correctly is missing.

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% and the id description already distinguishes asset ids from generation ids and points to outputMediaUrl. The description adds only 'by id' with no further syntax, format, or example, so it neither repeats harmfully nor compensates meaningfully.

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 with scope: 'Get a download link for one asset's original media file, by id.' The 'original media file' qualifier and 'by id' scoping separate it cleanly from assets_get, which returns details and a media url.

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 states the selecting condition ('use it when the user wants to download or save the file') and names the two adjacent alternatives with their purposes: assets_get for details/media url, assets_get-playback-metadata for frame timing. An agent can route without opening other schemas.

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

Deploy Server

Other Tools