Skip to main content
Glama

Import released songs

import_songs

Bring in released songs of a linked artist by their track ids, without uploading Each track (list_released_songs: id) becomes an import: Kinetune fetches the song’s audio (about half a minute each), then the song is made with the release’s title and cover and analyzed like an upload; poll get_song_import or list_song_imports (status queued, fetching, done with song_id, or failed with why). A song we can’t fetch fails, and the user adds the file to it instead (add_song_import_audio). Songs already in the workspace or being imported are skipped (skipped: track_id and reason). Up to 50 at once, and a daily number per workspace (429 daily_limit). Only the user’s own songs: confirm they own or have the rights to them. Needs an active plan (402 plan_required without one; get_account: plan.active) and room in its storage (402 storage_full when it would not fit; get_account: storage). Without a plan, the user’s free song covers one import.

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": {
      "artist_id": "<artist_id>",
      "track_ids": "<track_ids>"
    },
    "name": "import_songs"
  }
}

Input Schema

NameRequiredDescriptionDefault
artist_idYesThe artist id
track_idsYesThe released songs’ ids (list_released_songs)
distinct_track_idsNoSelected releases the user confirmed are distinct from possible duplicates

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / distinct_track_ids
      Added value: +{
      +  "description": "Selected releases the user confirmed are distinct from possible duplicates",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 50,
      +  "type": "array"
      +}
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only say it is a non-read-only, non-destructive, non-idempotent open-world call; the description goes well beyond that with async job states (queued, fetching, done with song_id, failed with why), per-item skip records, a 50-item batch cap plus a daily per-workspace quota with a 429 daily_limit code, 402 plan_required/storage_full conditions, and a free-cover fallback. It stops short of saying what a retry of a partially completed call does, but the skip rule ('already in the workspace or being imported are skipped') effectively signals duplicate handling.

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?

The core action and its constraint are front-loaded in the first sentence, and there is essentially no filler — every clause carries an error code, limit, or follow-up tool. It is, however, a dense run-on with an awkward mid-sentence shift ('without uploading Each track...'), which slightly hurts scannability.

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 carries the return burden and does: it enumerates import statuses, the skipped result shape (track_id and reason), and the failure remediation path. Plan, storage, quota, and ownership constraints round out everything an agent needs to call this correctly.

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%, so the baseline is 3. The description usefully restates that track ids come from list_released_songs and that up to 50 are allowed, but it never addresses the third parameter, distinct_track_ids, so an agent must infer its purpose from the schema text alone.

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 ('Bring in released songs of a linked artist by their track ids, without uploading') and immediately distinguishes the operation from create_upload by contrasting import-vs-upload semantics. It also names the id source (list_released_songs) so the agent knows which sibling feeds it.

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 routes the agent: ids come from list_released_songs, progress is polled via get_song_import or list_song_imports, and fetch failures are handled by switching to add_song_import_audio. It adds prerequisites (active plan via get_account: plan.active, storage room) and states what happens when they are unmet, leaving little to inference.

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