Skip to main content
Glama

Organize a Library file

update_media
Destructive

Rename a file in the artist's Library, give it a short description, set the artist's own tags, or link it to one song or album, as the file's Edit in the Library does. Only what you pass changes; tags replaces the whole set. It overwrites what was there (the answer says what it was), so tell the artist what you change. Limits: name 120 characters, description 500, up to 20 tags of 40 characters, stored lowercase.

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": {
      "media_asset_id": "<media_asset_id>"
    },
    "name": "update_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoThe file's name; null goes back to its own name.
tagsNoThe artist's own tags, the whole set; [] clears them.
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.
unlinkNotrue: take it off its song or album.
album_idNoLink it to this album (from list_albums). Clears a song link.
track_idNoLink it to this song (from list_tracks). Clears an album link.
descriptionNoA few words about it; null clears it.
media_asset_idYesFrom list_media.
idempotency_keyNoSend the same key if you retry, and the change happens once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description earns its credit by explaining the destructive mechanics: prior values are overwritten and the response returns what they were, so the agent can report the change. It also adds hard limits (120-char name, 500-char description, 20 tags of 40 chars, lowercase storage) that appear nowhere in the schema. It does not discuss permissions or the label-connection requirement in the description, though the artist parameter covers that in the schema.

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 capabilities before the constraints, and every clause carries information (partial-update semantics, overwrite warning, limits). The first sentence is long and clause-heavy, which slightly hurts scanability, but nothing is filler.

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?

For a 9-parameter destructive mutation with no output schema, the description covers what changes, how tags differ from a merge, that old values are returned, the size limits, and the advisory to inform the artist. Combined with full schema coverage, an agent has everything needed to call this correctly and report the result.

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 100%, so the baseline is 3, and the description adds meaning beyond it: the length and count limits per field and the fact that tags are stored lowercase are constraints the schema does not state. It reinforces replacement semantics for tags and the mutual exclusivity implied by linking to a song or album, though it does not spell out the song/album clearing interaction that the schema notes.

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 opens with a concrete verb and resource ('Rename a file in the artist's Library') and enumerates the editable facets: name, description, tags, and song/album link. It anchors the behavior to a known UI concept ('as the file's Edit in the Library does'), which makes the scope unambiguous. It stops short of naming sibling tools like update_track or update_album, so the agent must infer the boundary between a media file and a track/album entity.

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?

It gives useful operating guidance ('Only what you pass changes', 'tell the artist what you change') and warns that tags is a full replacement rather than a merge, which prevents a common misuse. However, there is no explicit when-to-use/when-not or pointer to an alternative tool (e.g., delete_media, tidy_library, update_track) when the target is not a Library file. Usage is implied by the resource description rather than stated as routing rules.

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