mcp-lyricscom

Get full lyrics

get_lyrics

Read-onlyIdempotent

Fetch full song lyrics from lyrics.com by numeric ID or URL, with offset continuation for long texts and optional word highlighting. Cites source URL and returns no_lyrics status when absent.

Instructions

Fetch the full lyrics of one song from lyrics.com, given the song id or URL returned by search_lyrics or search_songs. Lyrics can be long, so the response is truncated by default: check 'truncated' and call again with 'offset' set to 'next_offset' to continue reading. Some lyrics.com pages legitimately have no lyrics on file; those come back with status "no_lyrics" and an empty lyrics field, which is a valid answer and not an error, so do not retry them. Always cite 'source_url' and the artist when showing lyrics to a user.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	No	lyrics.com numeric song id, as returned by the search tools. Preferred over 'url'.
`url`	No	Full lyrics.com song URL. Only www.lyrics.com URLs are accepted. Ignored when 'id' is given.
`offset`	No	Character offset to resume from, for lyrics longer than max_chars.
`highlight`	No	Optional word. When set, the response reports whether it appears in the lyrics and on which line.
`max_chars`	No	Maximum characters of lyrics text to return in this call.

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes
`notes`	Yes
`title`	Yes
`artist`	Yes
`lyrics`	Yes	Slice of the lyrics text. Empty when status is 'no_lyrics'.
`offset`	Yes
`source`	Yes
`status`	Yes
`highlight`	Yes
`truncated`	Yes
`line_count`	Yes
`source_url`	Yes
`attribution`	Yes	Ready-to-display credit line.
`next_offset`	Yes
`total_chars`	Yes
`returned_chars`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedv2.0.0Aug 26, 2026

addedInput schema / properties / offset / maximum
```
Added value: +9007199254740991
```

addedOutput schema / properties / artist / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / artist / type
```
Removed value: -[
-  "string",
-  "null"
-]
```

changedOutput schema / properties / highlight / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "found": {
-        "type": "boolean"
-      },
-      "line": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "line_number": {
-        "anyOf": [
-          {
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "word": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "word",
-      "found",
-      "line_number",
-      "line"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "found": {
+        "type": "boolean"
+      },
+      "line": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "line_number": {
+        "anyOf": [
+          {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "word": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "word",
+      "found",
+      "line_number",
+      "line"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / line_count / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / line_count / minimum
```
Added value: +-9007199254740991
```

changedOutput schema / properties / next_offset / anyOf

Previous value: -[
-  {
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / offset / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / offset / minimum
```
Added value: +-9007199254740991
```
addedOutput schema / properties / returned_chars / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / returned_chars / minimum
```
Added value: +-9007199254740991
```

addedOutput schema / properties / title / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / title / type
```
Removed value: -[
-  "string",
-  "null"
-]
```
addedOutput schema / properties / total_chars / maximum
```
Added value: +9007199254740991
```
addedOutput schema / properties / total_chars / minimum
```
Added value: +-9007199254740991
```

Changed2 schema fields changedv1.4.0Aug 11, 2026

addedOutput schema / properties / notes

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "status",
-  "id",
-  "title",
-  "artist",
-  "source_url",
-  "lyrics",
-  "total_chars",
-  "returned_chars",
-  "offset",
-  "next_offset",
-  "truncated",
-  "line_count",
-  "highlight",
-  "attribution",
-  "source"
-]New value: +[
+  "status",
+  "id",
+  "title",
+  "artist",
+  "source_url",
+  "lyrics",
+  "total_chars",
+  "returned_chars",
+  "offset",
+  "next_offset",
+  "truncated",
+  "line_count",
+  "highlight",
+  "attribution",
+  "source",
+  "notes"
+]

First observedv1.0.0Aug 3, 2026

TDQS

A4.9/5.0

Behavior5/5

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

The annotations already establish read-only, non-destructive, and idempotent behavior. The description adds valuable behavioral details beyond those: truncation with a 'truncated' flag, continuation via 'next_offset', and the legitimate 'no_lyrics' status with empty lyrics. It also specifies attribution requirements, going well beyond what annotations convey.

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?

The description is four focused sentences, each contributing essential information: the core action, pagination behavior, a critical edge case, and a user-facing citation requirement. It is front-loaded with the main purpose and avoids filler, making it easy for an agent to parse quickly.

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?

For a read-only retrieval tool with an output schema and no required parameters, the description covers everything needed: how to specify the target, how to handle long lyrics, how to interpret a legitimately empty result, and what to show users. The presence of an output schema means return-value details like 'source_url' and 'truncated' do not need to be repeated here.

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

Parameters4/5

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

Schema coverage is 100%, so each parameter is already documented. The description adds practical semantics by explaining that id/url come from the search tools, that id is the preferred option, and that 'offset' should be set to the previously returned 'next_offset' for continued reading. This gives the agent more operational context than the schema alone.

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 ('Fetch') with a concrete resource ('full lyrics of one song from lyrics.com') and explicitly ties the required input to the sibling search tools. This clearly distinguishes get_lyrics from search_songs and search_lyrics, which find songs or lyrics pages rather than retrieving a specific song's lyrics.

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 states that the tool should be called with an id or URL returned by search_lyrics or search_songs, giving a concrete precondition. It also provides an exclusion by explaining that a 'no_lyrics' response is a valid outcome and should not be retried, which is actionable and prevents unnecessary repeated calls.

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

Deploy Server