Skip to main content
Glama

Delete a Library file

delete_media
Destructive

Delete one file from the artist's Library for good, with its stored file. Ask the artist first and name the file: it cannot be brought back. Refused while the file is in use (a song's or album's cover, the logo, the profile photo, an Artist page photo, or any Promo post: draft, approved, scheduled or posted); the refusal names each use and post, so the artist can change those first.

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

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.
media_asset_idYesFrom list_media.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds crucial context beyond them: the deletion is permanent and irreversible, the stored file is removed too, and the operation is blocked while the asset is referenced, with the exact reference categories listed. It even discloses the refusal payload naming each use and post, which is behavior an agent cannot infer from annotations.

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 the action and the irreversibility warning, then the refusal conditions, which is the right order for a destructive tool. The long parenthetical enumeration of in-use cases is dense but each item earns its place by preventing a failed call; slightly tighter phrasing would improve it.

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 two-parameter destructive tool with no output schema, the description covers action, irreversibility, confirmation protocol, and the full failure mode with its remediation path. Nothing an agent needs to call this correctly or interpret a refusal 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 description coverage is 100%, with artist and media_asset_id both documented in the schema, so the schema does the heavy lifting. The description adds only the imperative to 'name the file' before deleting, and says nothing extra about media_asset_id provenance or the label-only artist parameter. Baseline 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?

Names a specific verb and resource ('Delete one file from the artist's Library') and adds scope ('with its stored file'), making it clearly distinct from get_media_file, update_media, and list_media. An agent can tell it is the removal operation without opening any 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?

Gives explicit preconditions before invoking ('Ask the artist first and name the file') and enumerates the situations where the call is refused, effectively telling the agent when not to attempt deletion. It stops short of naming sibling tools (e.g. update_media for reassigning a cover), but the routing via 'change those first' is implied clearly enough for practical use.

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