Skip to main content
Glama

List an artist’s released songs

list_released_songs
Read-onlyIdempotent

The linked artist’s songs in the music catalog, each saying whether it is already in Kinetune Newest release first; an EP or album’s tracks in order. Each has id (the track_id to import), title, release (name, kind single, ep or album, date; a date of null is announced, not out yet), track_number, duration_seconds, cover_url (up to 3000 px), song_id when it is already in the workspace, possible_duplicates for close title and duration matches, and import while it is being imported (status, error). q narrows them to a title or release. The artist must be linked first (409 artist_not_linked: find_artist_in_catalog, then link_artist).

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>"
    },
    "name": "list_released_songs"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoPart of a title or release name
artist_idYesThe artist id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/closed-world annotations, it discloses ordering (newest release first, EP/album tracks in order), the meaning of release.date = null (announced but not out), duplicate detection, and in-flight import status. That is real behavioral context an agent cannot get from the annotations. It does not mention result limits or how a partial-import entry should be treated during selection.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the prose is a run-on with broken punctuation ('...already in Kinetune. Newest release first; an EP or album's tracks in order.') and a long comma-spliced field enumeration that slows parsing. Every field listed is useful given no output schema, but the presentation obscures the structure.

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 no output schema, the description correctly compensates by documenting each returned field and the date-null and duplicate semantics. It covers ordering, filtering, and the linking precondition. What remains unstated is pagination/volume behavior for a large discography, which matters for a listing tool.

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 already 100%, and the q note essentially restates the schema's own description. The only added parameter meaning is that artist_id must reference a linked artist, which the 409 guidance implies rather than defines. Baseline 3 is appropriate when the schema carries the load.

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 definition opens with a concrete verb+resource+scope: the linked artist's songs in the music catalog, annotated with whether each is already in Kinetune. It is clear what the call returns, but it never names a sibling such as list_songs or show_songs, so the agent must infer the difference between catalog-released tracks and workspace songs from field hints (song_id) alone.

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 gives an explicit prerequisite path for the failure case: the artist must be linked first, and on 409 artist_not_linked the agent is routed to find_artist_in_catalog then link_artist — a rare, genuinely actionable alternative. It also states q narrows by title or release, but stops short of saying when to prefer this over other listing tools.

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