Skip to main content
Glama

List a song’s covers

list_song_covers
Read-onlyIdempotent

Every cover the song has had, made or uploaded, the one in use marked, and what making more costs Newest first; each cover is kept until deleted (delete_cover). in_use is the cover the song uses; any other can be put back in use (use_cover). A made cover (source made, ai_made true) has the idea it came from (title, pitch, style, director_pick). download_url saves its full size (full_size px square: 3000 for a made cover). rounds: covers being made now (make_cover), and the newest round if it failed. can.plan: making covers needs a paid plan; can.ready: the song is analysed; can.artist: the artist can be on a cover (they have a character). price.counts: the credits for 1 to 4 covers; price.redraw: redrawing one with a note. artist_look: the colours and typeface the artist's covers keep, once their first made cover is used.

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": {
      "song_id": "<song_id>"
    },
    "name": "list_song_covers"
  }
}

Input Schema

NameRequiredDescriptionDefault
song_idYesThe song id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior5/5

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

Beyond the annotations, which already state readOnlyHint=true, idempotentHint=true, and destructiveHint=false, the description adds substantial behavior: newest-first ordering, persistence until deletion, in_use semantics, made-cover source metadata, download size, active/failed rounds, plan/readiness/artist flags, pricing, and artist look. These details materially help an agent understand what the list returns and what prerequisites affect follow-up actions, with no contradiction of the annotations.

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?

The description is information-dense and largely free of filler, and it front-loads the core listing purpose before covering related operations. However, it is written as a single run-on construction with terse fragments such as 'can.plan' and 'can.ready,' which reduces clarity and scanability.

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?

Because there is no output schema, the description must carry the return-value burden, and it does so extensively by naming ordering, in_use, made-cover idea fields, download_url full size, rounds, can flags, pricing, and artist_look. It does not spell out the full response object or any pagination behavior, but it is complete enough for an agent to select and invoke the tool 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?

There is a single required parameter, song_id, and the schema description coverage is 100%, with the schema itself defining it as 'The song id.' The tool description adds no additional meaning, constraints, or format guidance for song_id, so the baseline score of 3 is appropriate.

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 clearly identifies the resource and scope: 'Every cover the song has had, made or uploaded,' with the in-use cover marked. It also names related sibling operations such as delete_cover, use_cover, and make_cover, which helps distinguish this as the read/list operation, though it never explicitly says 'use this tool to list covers' or contrasts directly with get_song.

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 by references to deleting, using, and making covers, so an agent can infer this is for inspecting covers, costs, readiness, and artist look before taking those actions. However, there is no explicit when-to-use or when-not-to-use guidance, nor a direct alternative such as get_song for song metadata.

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