Skip to main content
Glama

Get lyrics

get_lyrics
Read-onlyIdempotent

Fetch lyrics for a track from LRCLIB by ID or artist/title, with plain or synced timestamped formats, and pagination for long lyrics.

Instructions

Fetch the lyrics of one track from LRCLIB, given the id returned by search_tracks, or an exact artist and title. Set 'format' to "synced" for karaoke-style lyrics with a timestamp on every line, "plain" for the text alone, or "both". Check 'has_synced_lyrics' in the search results first: not every track has timed lyrics. Lyrics can be long, so the text is truncated by default: check 'truncated' and call again with 'offset' set to 'next_offset' to continue reading. Instrumental tracks come back with status "instrumental" and no text, which is a valid answer, so do not retry them. Always cite 'attribution' when showing lyrics to a user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoLRCLIB track id, as returned by search_tracks. Preferred over the name fields.
formatNo'plain' returns the text only. 'synced' returns LRC text plus a parsed list of timestamped lines. 'both' returns each of them.plain
offsetNoCharacter offset to resume from, for lyrics longer than max_chars.
max_charsNoMaximum characters of lyrics text to return in this call.
album_nameNoAlbum name, to pick between releases.
track_nameNoSong title, matched exactly by LRCLIB. Required when 'id' is absent.
artist_nameNoArtist name, matched exactly by LRCLIB. Required when 'id' is absent.
duration_secondsNoTrack duration, to pick between versions of differing length.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesYes
trackYes
offsetYes
sourceYes
statusYes
truncatedYes
attributionYes
next_offsetYes
total_charsYes
plain_lyricsYes
synced_linesYesParsed timestamped lines.
synced_lyricsYesRaw LRC text, one timestamp per line.
paginated_formYesWhich body the character counts and the offset describe. Timed text carries its timestamps, so it is longer than the words alone.
returned_charsYes
synced_lines_truncatedYes
Behavior5/5

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

Despite readOnlyHint and idempotentHint annotations, the description adds substantial behavioral context: default truncation with 'truncated' and 'next_offset', instrumental status returning no text, and the requirement to cite 'attribution'. No contradiction with annotations.

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

Conciseness5/5

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

A single paragraph that is front-loaded with purpose, then efficiently covers input methods, format options, truncation behavior, edge cases, and attribution. Every sentence earns its place without fluff or redundancy.

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?

Covers the full workflow: how to obtain input (search_tracks), pre-checks (has_synced_lyrics), format selection, pagination/truncation, instrumental edge case, and attribution requirement. Combined with the rich output schema and annotations, the description leaves no critical gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even with 100% schema coverage, the description enriches parameter meaning: explains the 'format' enum values in user terms, clarifies that 'id' is preferred over name fields, and mentions duration_seconds for disambiguation. This adds value beyond the schema.

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?

The description opens with a specific verb and resource: 'Fetch the lyrics of one track from LRCLIB.' It clearly distinguishes from siblings by focusing on lyric content and explicitly references search_tracks as the source of the id, leaving no ambiguity about what this tool does.

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?

Provides explicit workflow guidance: use the id from search_tracks or exact artist/title, check 'has_synced_lyrics' first, and do not retry instrumental tracks. This is actionable when-to-use and when-not-to-use guidance that goes beyond generic alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smeet666/mcp-lrclib'

If you have feedback or need assistance with the MCP directory API, please join our Discord server