Skip to main content
Glama

Get a song

get_song
Read-onlyIdempotent

One song and its analysis status cover_art.url is the cover at up to 1536 px (JPEG; width and height describe it), preview_url a 640 px and thumbnail_url a 160 px WebP; cover_art is null for a song without cover art (it is optional). Image links are signed for 7 days and stay the same all day, so they can be cached. analysis.lyrics.status says whose words its videos show: "transcribed" (as heard), "checked" (your lyrics, timed from the audio; corrected, added and kept count what checking did), "waiting" (your lyrics, checked once the analysis finishes) or "mismatch" (your lyrics didn’t match what’s sung, so the transcription is used). brief: what the song is about as every director reads it (theme, tone, story, mood_arc by section, setting), null before the analysis; status writing while it is written (a song analysed without one has it started by this call: get it again in half a minute), edited true once the user corrected it (edit_song_brief).

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

Input Schema

NameRequiredDescriptionDefault
song_idYesThe song id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

The text is rich on behavior: signed image URLs valid 7 days and cacheable, lyrics status meanings, and the side effect that calling this on a song analysed without a brief starts brief writing. That last point conflicts with readOnlyHint=true, since the call initiates a server-side write; the disclosure protects the agent, but the definition and annotations disagree about whether this tool mutates state.

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?

Information density is high and every clause carries content, but it is a single unbroken block of semicolon- and parenthesis-laden field documentation rather than a front-loaded purpose statement followed by details. Return-field semantics dominate the opening, pushing the key behavioral fact (the brief-writing side effect) to the very end.

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, documenting cover_art/preview_url/thumbnail_url sizes and formats, URL signing lifetime, the four lyrics status values, and brief subfields is genuinely necessary and is done thoroughly. Gaps remain around error behavior for a bad id and what sibling tool to use for analysis-only retrieval.

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?

Only song_id is accepted and schema coverage is 100%, so the schema already carries the parameter meaning. The description adds nothing about id format, validity, or what happens with an unknown or malformed id, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening 'One song and its analysis status' identifies the resource and rough scope, but it is a noun fragment rather than a stated verb+resource, and the bulk of the text documents returned fields. It never distinguishes this tool from the sibling get_song_analysis, which an agent would plausibly consider for the same goal.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use statement and no comparison against alternatives such as get_song_analysis. The only implicit guidance is operational: re-fetch after about half a minute while brief.status is 'writing', and use edit_song_brief to correct a brief.

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