Skip to main content
Glama

The artist's Library

list_media
Read-onlyIdempotent

The artist's pictures or videos in Audora's Library, newest first. Search by name, description and the artist's own tags; filter by category (Brand kit, Logo, Cover art, Promo, a platform, Made by Audora, Uploaded, Found online, Stock footage), by the song, album or release a file belongs to, by the artist's own tags, or to files no Promo post uses. Each has a media_asset_id (what update_post takes), its description, tags and links, and a preview link valid for an hour.

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": "list_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoPictures (default) or videos.
tagsNoThe artist's own tags: only files that carry every one.
limitNo
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.
offsetNo
searchNoWords in the file's name, description or the artist's own tags, or the title of the song or album it belongs to.
album_idNoOnly files linked to this album (from list_albums).
track_idNoOnly files linked to this song (from list_tracks).
categoriesNoOnly files in every one of these.
release_idNoOnly files linked to this release or to its song or album (from list_releases).
not_in_postsNotrue: only files no Promo post uses, whatever the post's status.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / album_id
      Added value: +{
      +  "description": "Only files linked to this album (from list_albums).",
      +  "type": "string"
      +}
    • changedInput schema / properties / categories / description
      Previous value: -"Only items in every one of these."New value: +"Only files in every one of these."
    • addedInput schema / properties / not_in_posts
      Added value: +{
      +  "description": "true: only files no Promo post uses, whatever the post's status.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / release_id
      Added value: +{
      +  "description": "Only files linked to this release or to its song or album (from list_releases).",
      +  "type": "string"
      +}
    • changedInput schema / properties / search / description
      Previous value: -"Words in the item's name, or the artist, track or album it belongs to."New value: +"Words in the file's name, description or the artist's own tags, or the title of the song or album it belongs to."
    • addedInput schema / properties / tags
      Added value: +{
      +  "description": "The artist's own tags: only files that carry every one.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / track_id
      Added value: +{
      +  "description": "Only files linked to this song (from list_tracks).",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • changedInput schema / properties / categories / items / enum
      Previous value: -[
      -  "branding",
      -  "logo",
      -  "cover-art",
      -  "promo",
      -  "tiktok",
      -  "instagram",
      -  "youtube",
      -  "facebook",
      -  "ai-generated",
      -  "uploaded",
      -  "stock"
      -]New value: +[
      +  "branding",
      +  "logo",
      +  "cover-art",
      +  "promo",
      +  "tiktok",
      +  "instagram",
      +  "youtube",
      +  "facebook",
      +  "ai-generated",
      +  "uploaded",
      +  "found-online",
      +  "stock"
      +]
  3. First observed

TDQS

A3.8/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 context beyond that: newest-first ordering, the field set returned, and a preview link that is valid for only one hour — a genuinely useful operational constraint an agent would otherwise not know.

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?

Two sentences, front-loaded with the resource and ordering, then the filtering and return-value detail. The second sentence is dense — categories, linkage filters and return fields packed together — but each clause carries information rather than 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?

With 11 optional parameters and no output schema, the description does the right work: it enumerates what each file record contains and gives an example of how the id is consumed downstream. Pagination behavior (limit max 50, offset) is left entirely to the schema, and the label-vs-artist connection requirement on the artist param is also schema-only, which is a minor gap for a tool of this size.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 82%, so the baseline is 3. The description nevertheless adds meaning: it translates the opaque enum values into human labels (branding to Brand kit, ai-generated to Made by Audora, stock to Stock footage) and clarifies that tags and categories use AND semantics ('every one') and that not_in_posts ignores post status.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete resource and scope: the artist's pictures or videos in Audora's Library, returned newest first, with search and filter capabilities spelled out. It does not name a sibling it is not (e.g. get_media_file for a single file or find_online for web lookups), so the boundary with adjacent tools must be inferred from the resource alone.

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

Usage Guidelines3/5

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

Usage is implied through the filter vocabulary (search, category, song/album/release, tags, not_in_posts) rather than stated as when-to-use guidance. There is one useful downstream cue — the returned media_asset_id is what update_post takes — but no explicit when-not or alternative-tool routing.

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