Last Fm

Track Search

track_search

Read-onlyIdempotent

Search Last.fm for tracks matching a keyword query; returns ranked results with artist, track name, and listener counts.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`results`	No	Search results container

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "imagine john lennon"
+  },
+  {
+    "limit": 5,
+    "query": "stairway to heaven"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "description": "Search results container",
+      "properties": {
+        "@attr": {
+          "properties": {
+            "for": {
+              "type": "string"
+            },
+            "page": {
+              "type": "string"
+            },
+            "perPage": {
+              "type": "string"
+            },
+            "total": {
+              "type": "string"
+            },
+            "totalPages": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "trackmatches": {
+          "properties": {
+            "track": {
+              "description": "Array of matching tracks",
+              "items": {
+                "properties": {
+                  "artist": {
+                    "description": "Artist name",
+                    "type": "string"
+                  },
+                  "image": {
+                    "items": {
+                      "properties": {
+                        "#text": {
+                          "type": "string"
+                        },
+                        "size": {
+                          "type": "string"
+                        }
+                      },
+                      "type": "object"
+                    },
+                    "type": "array"
+                  },
+                  "listeners": {
+                    "description": "Number of listeners",
+                    "type": "string"
+                  },
+                  "name": {
+                    "description": "Track name",
+                    "type": "string"
+                  },
+                  "url": {
+                    "description": "Track URL",
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare it as read-only, idempotent, and non-destructive. The description adds that results are ranked and include artist, track name, and listener counts, which goes beyond the structured annotations. However, it does not disclose any additional behavioral aspects like authentication or rate limits.

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 a single sentence that immediately conveys the tool's purpose, source, action, and result format. No extraneous information; every word adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (2 parameters, output schema present, rich annotations), the description covers the main purpose and result structure. However, it omits explanation of the 'limit' parameter, which is a notable gap for a complete understanding. The output schema covers return values, so return format is sufficiently documented.

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

Parameters2/5

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

With 0% schema coverage, the description should explain both parameters. It only implicitly explains 'query' as a 'keyword query' but says nothing about 'limit' (e.g., max results, default value). The description focuses on output rather than input, leaving one parameter undocumented.

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 clearly states the tool searches Last.fm for tracks by keyword query and returns ranked results with specific fields (artist, track name, listener counts). It distinguishes this from sibling tools like track_info (which likely returns detail for a specific track) and artist_top_tracks (which is artist-specific).

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 implies usage when a keyword-based track search is needed, contrasting with more specific lookup tools. It does not explicitly state when not to use, but the context of sibling tools and the clear purpose provide adequate guidance.

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

All Last Fm tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.