Skip to main content
Glama

Download a Library file

get_media_file
Read-onlyIdempotent

A download link, valid an hour, for one file: a picture or video in the artist's Library (media_asset_id from list_media), or the picture or video on a post (post_id), such as a video Audora made. For a video made without the song (sound none), it also gives the caption and the steps to post it in the app with the song's official sound.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_media_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
artistNoOnly when you are connected as a label: the roster artist this call is for — their artist_user_id from list_roster, or their exact artist name. Required for every artist tool on a label connection. Leave it out on an artist's own connection.
post_idNoA post whose picture or video to download (get_campaign or promo_this_week).
media_asset_idNoA Library item (list_media).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real behavioral value on top: the link expires after one hour, and for a video made without the song it returns the caption plus in-app posting steps — non-obvious output shape the 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-loaded with the most important fact (a one-hour download link for a single file), followed by the source options and then the edge case for soundless videos. Slightly dense phrasing ("For a video made without the song (sound none)") but no wasted sentences.

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?

There is no output schema, so the description carries the return-value burden, and it does describe both the link and the extra caption/steps payload. It falls short of fully complete only in not clarifying the post_id versus media_asset_id exclusivity or failure behavior when neither is provided.

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 the per-parameter ID provenance (list_media, get_campaign, roster) is already documented and the description largely repeats it. A notable gap remains: with zero required parameters, the description never states that exactly one of post_id or media_asset_id should be supplied, nor what happens if both or neither are given.

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 the concrete deliverable (a download link for exactly one file) and enumerates the two distinct sources: a Library asset (media_asset_id from list_media) or a post's picture/video (post_id). It also names the sibling tools that supply those IDs, so an agent can distinguish it from list_media, get_campaign, and get_stats without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly signals the two usage paths and where to obtain the identifier for each, which functions as when-to-use guidance. It stops short of explicit exclusions (e.g., what to do if the file is on a post versus in the Library, or what not to use for listing) but the context is unambiguous for a fetch-style tool.

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