mcp-lyricscom

Get full lyrics

get_lyrics

Read-onlyIdempotent

Fetch full song lyrics from lyrics.com using a song ID or URL. Retrieve the complete text, resume long lyrics with an offset, and optionally check whether a specific word appears and on which line.

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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_lyrics"
  }
}

Input 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

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.

Changed5 schema fields changedv2.1.0Oct 30, 2026

removedOutput schema / properties / artist / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / artist / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / highlight / anyOf

Previous 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"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "found": {
+        "type": "boolean"
+      },
+      "line": {
+        "type": [
+          "string",
+          "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"
+  }
+]

removedOutput schema / properties / title / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / title / type
```
Added value: +[
+  "string",
+  "null"
+]
```

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?

Annotations already declare read-only/idempotent/open-world, so the description goes beyond them usefully: it discloses the default truncation behavior, the pagination continuation contract, and the legitimate 'no_lyrics' + empty-field response that must not be retried. That last point is the kind of non-obvious behavior that prevents an agent from looping on a valid empty result.

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?

Front-loaded with the core action, then pagination, then the no_lyrics caveat, then the citation rule — each sentence addresses a distinct failure mode. No restatement of the title or annotations, and no filler.

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?

Five optional parameters, an output schema, and full annotation coverage are all accounted for; the description supplies exactly the pieces structured fields cannot — continuation protocol, empty-result semantics, and attribution policy. An agent could call this correctly on the first attempt.

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 all five parameters are already documented including the id-over-url preference and the max_chars default. The description adds cross-parameter workflow semantics the schema cannot express — the truncated/next_offset relationship and the offset continuation loop — which lifts it above the baseline 3, though it does not explain highlight or max_chars bounds.

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+resource ('Fetch the full lyrics of one song from lyrics.com') and explicitly names the inputs' provenance ('id or URL returned by search_lyrics or search_songs'). This makes it immediately distinguishable from the two search siblings, which return ids rather than 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?

Explicitly routes from the siblings into this tool, prescribes the truncation workflow ('check truncated and call again with offset set to next_offset'), and states a when-NOT-to-retry rule for the no_lyrics status. It also states a post-condition obligation (cite source_url and artist). Nothing about when/how to call is left to inference.

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

Deploy Server