mcp-lrclib

Get track metadata

get_track

Read-onlyIdempotent

Look up an LRCLIB track by ID to return title, artist, album, duration, and lyric availability without fetching lyrics—confirm the right release before requesting lyrics.

Instructions

Look up one LRCLIB track by its id and return its metadata without the lyrics: title, artist, album, duration, and whether plain and time-synced lyrics exist. Use this to confirm you have the right release or version before calling get_lyrics, or to check whether timed lyrics exist for a track id you already hold.

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": {
      "id": "<id>"
    },
    "name": "get_track"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	LRCLIB track id, as returned by search_tracks.

Output Schema

Name	Required	Description
`notes`	Yes
`track`	Yes
`source`	Yes
`duration_formatted`	Yes	Duration as m:ss, when known.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv2.1.0Oct 30, 2026
- removedOutput schema / properties / duration_formatted / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / duration_formatted / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / track / properties / album_name / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / track / properties / album_name / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / track / properties / duration_seconds / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / track / properties / duration_seconds / type
```
Added value: +[
+  "number",
+  "null"
+]
```
Changed9 schema fields changedv2.0.0Aug 26, 2026
- addedInput schema / properties / id / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / duration_formatted / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / duration_formatted / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / track / properties / album_name / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / track / properties / album_name / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
- addedOutput schema / properties / track / properties / duration_seconds / anyOf
```
Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / track / properties / duration_seconds / type
```
Removed value: -[
-  "number",
-  "null"
-]
```
- addedOutput schema / properties / track / properties / id / maximum
```
Added value: +9007199254740991
```
- addedOutput schema / properties / track / properties / id / minimum
```
Added value: +-9007199254740991
```
First observedv1.0.0Aug 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuine behavioral detail beyond that: the response omits lyrics, and it surfaces whether plain and time-synced lyrics exist — useful decision information. It stops short of noting error behavior for a missing/unresolvable id.

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?

Two sentences, zero padding, with the scope ('without the lyrics') and the return fields front-loaded before the usage guidance. Every clause earns its place.

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?

Output schema exists, so return-shape explanation is not required, and annotations carry the safety profile. For a single-parameter read tool the description supplies everything an agent needs to choose and invoke it 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 description coverage is 100%; the id parameter is already documented as 'LRCLIB track id, as returned by search_tracks.' The description only restates 'by its id' and adds no format, range, or provenance detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Look up one LRCLIB track by its id') and enumerates exactly what comes back (title, artist, album, duration, lyric-availability flags), explicitly noting lyrics are excluded. This distinguishes it cleanly from sibling get_lyrics and search_tracks without needing their schemas.

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?

Gives two concrete triggers: verifying the right release/version before calling get_lyrics, and checking whether time-synced lyrics exist for an id already held. The alternative (get_lyrics) is named alongside the condition that selects it.

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

Deploy Server