Last Fm

Track Info

track_info

Read-onlyIdempotent

Fetch Last.fm track metadata by artist and track name (or MusicBrainz ID): duration, listener/play counts, genre tags, and wiki summary.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mbid`	No
`track`	Yes
`artist`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`track`	No	Track information object

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "artist": "Nirvana",
+    "track": "Smells Like Teen Spirit"
+  },
+  {
+    "artist": "Queen",
+    "track": "Bohemian Rhapsody"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "track": {
+      "description": "Track information object",
+      "properties": {
+        "album": {
+          "properties": {
+            "artist": {
+              "type": "string"
+            },
+            "image": {
+              "items": {
+                "properties": {
+                  "#text": {
+                    "type": "string"
+                  },
+                  "size": {
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            },
+            "mbid": {
+              "type": "string"
+            },
+            "title": {
+              "type": "string"
+            },
+            "url": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "artist": {
+          "properties": {
+            "mbid": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            },
+            "url": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "duration": {
+          "description": "Duration in milliseconds",
+          "type": "string"
+        },
+        "listeners": {
+          "description": "Number of listeners",
+          "type": "string"
+        },
+        "mbid": {
+          "description": "MusicBrainz ID",
+          "type": "string"
+        },
+        "name": {
+          "description": "Track name",
+          "type": "string"
+        },
+        "playcount": {
+          "description": "Total play count",
+          "type": "string"
+        },
+        "url": {
+          "description": "Track URL",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior. Description adds detail about data source (Last.fm) and returned fields, which is helpful. No contradictions or missing critical traits.

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?

Single sentence that is front-loaded with purpose and comprehensively lists key outputs. No extraneous words.

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?

Given the tool's simplicity, description covers purpose, parameters, and return types. Output schema provides structure for return values, but description already lists all relevant fields. Complete for an agent to use correctly.

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?

Schema coverage is 0%, so description must compensate. It mentions 'artist and track name (or MusicBrainz ID)' but does not explain the mbid parameter format, optionality, or how it relates to artist/track. The schema shows mbid as optional but description implies it's an alternative; more clarity needed.

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?

Description clearly states verb 'Fetch', resource 'Last.fm track metadata', and key outputs (duration, counts, tags, summary). It distinguishes from sibling tools like 'track_search' and 'album_info' by specifying exact lookup by artist/track name or MusicBrainz ID.

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?

Description explains when to use (when you have artist and track name or MBID) but does not explicitly state when not to use or compare with alternatives like 'track_search'. However, the specificity is strong enough for an agent to infer usage.

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.