mcp-lrclib

Get track metadata

get_track

Read-onlyIdempotent

Look up a track by ID to retrieve metadata, confirm the correct release, and check whether plain or time-synced lyrics exist before fetching 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.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON 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.

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 non-destructive behavior, so the description is not required to repeat those. The description adds meaningful behavioral context by specifying the return excludes lyrics and includes existence flags for plain and time-synced lyrics, which is not derivable from the schema or annotations alone.

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 with no filler. The first sentence states the core action and return payload; the second provides focused usage guidance. Everything present 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?

The tool is simple, has a single fully documented parameter, rich annotations, and an output schema. The description adds the missing context around when to use the tool and what it returns, making the complete call scenario clear. Nothing necessary for correct invocation is omitted.

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 described as 'LRCLIB track id, as returned by search_tracks.' The description does not need to add further parameter detail, so the baseline of 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?

The description uses a specific verb 'Look up' with a clear resource ('one LRCLIB track by its id') and lists the returned fields, distinguishing this from get_lyrics by explicitly stating 'without the lyrics'. This makes the tool's function unambiguous and differentiates it from both siblings.

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?

The description explicitly states when to use this tool: 'confirm you have the right release or version before calling get_lyrics' and 'check whether timed lyrics exist for a track id you already hold.' It references the closest sibling (get_lyrics) as the next step, providing clear routing guidance.

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

Deploy Server