Skip to main content
Glama

Get a song’s analysis

get_song_analysis
Read-onlyIdempotent

Word-timed lyrics, tempo, beats, sections, hook and the parts a video can be cut to parts lists where a video can start and end without cutting a word: each section (Verse 1, Chorus 1…), clips of about 15 seconds cut between the lines of long sections (kind "clip", parent: its section) and each verse with the chorus after it (kind "pair"); pass a part’s start and end as a video’s trim (start_seconds, end_seconds), picking one at least as long as the video type’s minimum (a lyric video 8 seconds, a music video 15). default_part is the one the app starts on: the sung part nearest 15 seconds. lyrics.text is the song’s lyrics to edit: yours as you gave them, or the transcription a line per phrase (lyrics.yours says which). The analysis also listens for who sings: map.voices lists where someone other than the lead artist sings (voice "other": another solo voice; "group": a choir, a crowd or backing singers), and those words carry backing: true (music videos keep them off camera, never lip-synced by the artist); map.instrumental is true when no vocals were heard. A song analyzed before voices were heard has no map.voices until its first music video plan listens to it.

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_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
song_idYesThe song id
min_secondsNoThe parts for a video at least this long: a music video 15 (its clips are cut no shorter). Default 8, a lyric video

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / min_seconds
      Added value: +{
      +  "description": "The parts for a video at least this long: a music video 15 (its clips are cut no shorter). Default 8, a lyric video",
      +  "maximum": 600,
      +  "minimum": 8,
      +  "type": "number"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare read-only/idempotent/no-destruction, so the bar is lower, and the description still adds genuine behavioral context: lyrics.text may be the user's own lyrics or a transcription with lyrics.yours saying which, and a song analyzed before voices were heard has no map.voices until its first music video plan listens to it. That disclosure of conditionally-missing fields is valuable; it stops short of stating what happens for an unanalyzed or missing song.

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?

Every clause carries real information and the length is defensible for a complex analysis object with no output schema, but the text is one dense run-on block that opens mid-thought with a confusing phrase instead of front-loading what the tool returns. The content earns its place; the structure does not.

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 must carry the return shape, and it does: lyrics, tempo/beats/sections, part kinds (clip, pair) with parent relationships, default_part, and voice/instrumental maps. It omits error or not-yet-analyzed behavior and the untimed fields (tempo, beats) are only named, but overall it is sufficient to use 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?

Schema coverage is 100%, so the schema already documents both parameters, including min_seconds' default of 8 and the 15-second music-video case. The description largely restates that same meaning in prose and adds nothing new for song_id, so baseline 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 enumerates the concrete contents of the resource (word-timed lyrics, tempo, beats, sections, hooks, video-cuttable parts), which makes clear it returns an analysis object rather than the song itself. However, the opening clause is garbled ("the parts a video can be cut to parts lists where a video can start and end...") and it never names or contrasts with the obvious siblings get_song and reanalyze_song, so an agent must infer the boundary.

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?

There is real downstream guidance: pass a part's start/end as a video's trim (start_seconds, end_seconds) and choose a part at least as long as the video type's minimum (8s lyric video, 15s music video), which also explains min_seconds. But there is no explicit when-to-use-this-vs-alternatives statement and no mention of preconditions such as needing the song analyzed first, so usage is implied rather than stated.

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