Last Fm

Album Info

album_info

Read-onlyIdempotent

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

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`album`	No	Album information object

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "album": "Abbey Road",
+    "artist": "The Beatles"
+  },
+  {
+    "album": "The Wall",
+    "artist": "Pink Floyd"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "album": {
+      "description": "Album information object",
+      "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"
+        },
+        "mbid": {
+          "description": "MusicBrainz ID",
+          "type": "string"
+        },
+        "name": {
+          "description": "Album name",
+          "type": "string"
+        },
+        "playcount": {
+          "description": "Total play count",
+          "type": "string"
+        },
+        "tracks": {
+          "description": "Album tracks",
+          "properties": {
+            "track": {
+              "items": {
+                "properties": {
+                  "duration": {
+                    "type": "string"
+                  },
+                  "name": {
+                    "type": "string"
+                  },
+                  "rank": {
+                    "type": "string"
+                  },
+                  "url": {
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            }
+          },
+          "type": "object"
+        },
+        "url": {
+          "description": "Album URL",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds value by specifying the external data source (Last.fm) and the exact data returned. No contradictions with annotations.

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, information-dense sentence that covers all essential aspects: action, source, input, output. No superfluous words.

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

Completeness4/5

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

Given the annotations (readOnlyHint, openWorldHint, idempotentHint) and an output schema (not shown but present), the description provides sufficient context for a simple lookup tool. It does not mention pagination or limitations, but for album metadata this is acceptable.

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?

With 0% schema description coverage, the description must compensate. It clarifies that the mbid parameter is an alternative to the artist+album pair, and provides examples in the schema. This adds meaning beyond the bare schema, though individual parameter details could be richer.

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 specifies the action (fetching album metadata), the source (Last.fm), the required identifiers (artist and album name or MusicBrainz ID), and the returned data (track listing, counts, wiki, tags). It distinguishes itself from sibling tools like artist_info and track_info which target different entities.

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 when to use the tool (when album metadata is needed) but does not explicitly state when not to use it. However, the context from sibling tool names provides differentiation, and the description is clear enough for an agent to select it appropriately.

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.