Last Fm

Artist Info

artist_info

Read-onlyIdempotent

Fetch Last.fm artist profile by name (or MusicBrainz ID): biography, listener/play counts, similar artists, and genre tags; optionally in a specified language.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`artist`	No	Artist information object

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "artist": "The Beatles"
+  },
+  {
+    "artist": "Radiohead",
+    "lang": "en"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "artist": {
+      "description": "Artist information object",
+      "properties": {
+        "bio": {
+          "description": "Artist biography",
+          "properties": {
+            "content": {
+              "description": "Full bio content",
+              "type": "string"
+            },
+            "summary": {
+              "description": "Bio summary",
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "image": {
+          "description": "Artist images at various sizes",
+          "items": {
+            "properties": {
+              "#text": {
+                "description": "Image URL",
+                "type": "string"
+              },
+              "size": {
+                "description": "Image size (small, medium, large, extralarge)",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "mbid": {
+          "description": "MusicBrainz ID",
+          "type": "string"
+        },
+        "name": {
+          "description": "Artist name",
+          "type": "string"
+        },
+        "similar": {
+          "description": "Similar artists",
+          "properties": {
+            "artist": {
+              "items": {
+                "properties": {
+                  "name": {
+                    "type": "string"
+                  },
+                  "url": {
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            }
+          },
+          "type": "object"
+        },
+        "stats": {
+          "description": "Artist statistics",
+          "properties": {
+            "listeners": {
+              "description": "Number of listeners",
+              "type": "string"
+            },
+            "playcount": {
+              "description": "Total play count",
+              "type": "string"
+            },
+            "userplaycount": {
+              "description": "User's play count",
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "tags": {
+          "description": "Artist tags",
+          "properties": {
+            "tag": {
+              "items": {
+                "properties": {
+                  "name": {
+                    "type": "string"
+                  },
+                  "url": {
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            }
+          },
+          "type": "object"
+        },
+        "url": {
+          "description": "Last.fm artist URL",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the description consistently describes a fetch operation. It adds valuable context about the returned data fields and language option, which goes beyond annotations. No contradictions.

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, well-structured sentence that concisely covers the tool's purpose, inputs, and outputs without redundancy or fluff. Every phrase adds value.

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?

An output schema exists (not shown but indicated), so the description does not need to detail return formats. It mentions the main data fields (biography, counts, similar artists, tags) which matches typical expectations. Minor omissions like error conditions or rate limits are acceptable given the tool's simplicity and existing annotations.

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?

With 0% schema description coverage, the description must compensate. It clarifies that 'artist' can be a name or MBID and that 'lang' is optional. However, it does not explain the relationship between 'artist' and 'mbid' parameters (e.g., whether they are mutually exclusive or which takes precedence), leaving some ambiguity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool fetches a Last.fm artist profile with specific data fields (biography, listener/play counts, similar artists, genre tags) and mentions alternative identifiers (name or MusicBrainz ID). It distinguishes the tool's comprehensive profile from siblings like artist_similar but does not explicitly contrast with them, so it's clear but not perfectly differentiated.

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

Usage Guidelines3/5

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

The description implies usage for fetching full artist profiles with optional language but provides no explicit when-to-use or when-not-to-use guidance relative to sibling tools. There is no statement about prerequisites or alternatives, leaving the agent to infer context.

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.