mcp-lyricscom

Search songs by title

search_songs

Read-onlyIdempotent

Find songs by title on lyrics.com and return their artist, album, year, ID, and URL, enabling lyric retrieval and distinguishing covers or versions by different artists.

Instructions

Find songs on lyrics.com by their title. Returns candidate songs with artist, album, year, and the lyrics.com id and URL. Use this when someone names a song and you need its id to call get_lyrics, or to tell covers and versions by different artists apart. An optional 'artist' narrows the list. lyrics.com searches titles and lyrics together, so results are ranked and filtered locally by title match; use match="strict" to keep only genuine title matches.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`limit`	No
`match`	No	'strict' keeps only results whose title matches the query as a whole title, ignoring suffixes such as '(Remastered)'. 'loose' keeps anything lyrics.com returned, best match first.	loose
`title`	Yes	Song title, or part of it.
`artist`	No	Optional artist name, matched case-insensitively against each result.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page`	Yes
`notes`	Yes
`title`	Yes
`source`	Yes
`results`	Yes
`has_more`	Yes
`next_page`	Yes
`filtered_out`	Yes
`artist_filter`	Yes
`raw_result_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedv2.0.0Aug 26, 2026

addedOutput schema / properties / artist_filter / anyOf

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

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

changedOutput schema / properties / next_page / anyOf

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

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

addedOutput schema / properties / results / items / properties / album / anyOf

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

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

addedOutput schema / properties / results / items / properties / excerpt / anyOf

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

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

changedOutput schema / properties / results / items / properties / year / anyOf

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

First observedv1.0.0Aug 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior, and the description adds valuable non-obvious behavior: lyrics.com searches titles and lyrics together, so results are ranked and filtered locally by title match, with 'strict' needed to keep genuine title matches. This explains potential unexpected results beyond what the 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?

Three tightly written sentences cover purpose, return shape, use cases, and the matching caveat without wasted words. Key information is front-loaded in the first sentence, and 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?

The description is complete for a read-only search tool: it states what it returns, when to use it, how to constrain results, and why results may be noisy. With an output schema present and rich annotations, no essential calling information is missing.

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?

The schema already describes title, artist, and match, and the description reinforces artist narrowing and strict matching. However, it adds little about page and limit, and schema description coverage is only 60%, so the description doesn't fully compensate for the undeclared pagination parameters.

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 and resource: 'Find songs on lyrics.com by their title,' and explicitly lists the return fields (artist, album, year, id, URL), making the tool's function unmistakable. This also distinguishes it from the sibling get_lyrics and search_lyrics, since it returns song candidates rather than lyric content.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear usage triggers: use this when a user names a song and you need its id for get_lyrics, or when disambiguating covers and versions by different artists. It also explains the optional artist narrowing and the strict match mode. It does not explicitly mention when to prefer search_lyrics, so it stops short of complete alternative guidance.

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

Deploy Server