Skip to main content
Glama

Spotify

by io.github.pipeworx-io

Get Album

get_album
Read-onlyIdempotent

Fetch a Spotify album by album_id. Returns name, artists, release date, total tracks, label, genres, popularity, images, and full tracklist with track IDs and durations. Optional market filter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketNoMarket for availability
album_idYesSpotify album ID

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoAlbum ID
nameNoAlbum name
imagesNo
tracksNo
artistsNo
popularityNoPopularity 0-100
release_dateNoRelease date (YYYY-MM-DD)
total_tracksNoTotal tracks on album
release_date_precisionNoPrecision (year/month/day)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "album_id": "2noRn2Aes5aoNVsU6iWjc0"
+  },
+  {
+    "album_id": "2noRn2Aes5aoNVsU6iWjc0",
+    "market": "US"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "Album record with tracklist",
+  "properties": {
+    "artists": {
+      "items": {
+        "properties": {
+          "id": {
+            "description": "Artist ID",
+            "type": "string"
+          },
+          "name": {
+            "description": "Artist name",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "id": {
+      "description": "Album ID",
+      "type": "string"
+    },
+    "images": {
+      "items": {
+        "properties": {
+          "height": {
+            "description": "Image height pixels",
+            "type": "number"
+          },
+          "url": {
+            "description": "Image URL",
+            "type": "string"
+          },
+          "width": {
+            "description": "Image width pixels",
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "name": {
+      "description": "Album name",
+      "type": "string"
+    },
+    "popularity": {
+      "description": "Popularity 0-100",
+      "type": "number"
+    },
+    "release_date": {
+      "description": "Release date (YYYY-MM-DD)",
+      "type": "string"
+    },
+    "release_date_precision": {
+      "description": "Precision (year/month/day)",
+      "type": "string"
+    },
+    "total_tracks": {
+      "description": "Total tracks on album",
+      "type": "number"
+    },
+    "tracks": {
+      "properties": {
+        "href": {
+          "description": "API endpoint for tracks",
+          "type": "string"
+        },
+        "items": {
+          "items": {
+            "properties": {
+              "artists": {
+                "items": {
+                  "properties": {
+                    "id": {
+                      "description": "Artist ID",
+                      "type": "string"
+                    },
+                    "name": {
+                      "description": "Artist name",
+                      "type": "string"
+                    }
+                  },
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              "duration_ms": {
+                "description": "Duration in milliseconds",
+                "type": "number"
+              },
+              "id": {
+                "description": "Track ID",
+                "type": "string"
+              },
+              "is_playable": {
+                "description": "Playable in market",
+                "type": "boolean"
+              },
+              "name": {
+                "description": "Track name",
+                "type": "string"
+              },
+              "track_number": {
+                "description": "Track number on album",
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "limit": {
+          "description": "Items per page",
+          "type": "number"
+        },
+        "offset": {
+          "description": "Offset in results",
+          "type": "number"
+        },
+        "total": {
+          "description": "Total tracks",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so safety is established. The description adds the return field list, which is useful but not a behavioral trait beyond what annotations and output schema already provide. No additional side effects or limitations are disclosed.

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?

Two sentences, front-loaded with the core action, then a concise list of return fields. Every word earns its place; no filler.

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?

For a simple fetch tool with full schema coverage, comprehensive annotations, and an output schema, the description provides a complete summary. It covers what the tool does, what it returns, and the optional filter—sufficient for an agent to select and invoke correctly.

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?

Schema coverage is 100%—both album_id and market are described in the schema. The description mentions 'optional market filter,' which mirrors the schema's 'Market for availability' without adding new detail. Baseline 3 is appropriate.

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 ('Fetch') and resource ('Spotify album by album_id'), clearly distinguishing it from sibling tools like get_track or get_artist. It enumerates the returned data, leaving no ambiguity about scope.

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?

Clear context: this is the tool for fetching a full album by ID. It does not explicitly name alternatives or exclusions, but the album-specific scope implies when to use it. Lacks explicit 'use get_track for tracks' guidance.

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

All Spotify toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.1/5.0
Disambiguation1/5

The tool set is a chaotic mix of Spotify music tools and an extensive Pipeworx data querying system, with no clear separation. Tools like 'ask_pipeworx', 'ask_pipeworx_grounded', and 'deep_research' have overlapping querying purposes, while unrelated tools from prediction markets and company research further muddy the boundaries. An agent would struggle to distinguish which tool to use for a given task.

Naming Consistency2/5

Naming conventions are inconsistent: Spotify tools follow a verb_noun pattern (e.g., 'get_album', 'search'), while Pipeworx tools use descriptive phrases (e.g., 'ask_pipeworx', 'bet_research'). Additionally, some tools have vague names like 'process' or 'run' that could apply to anything. The lack of a unified naming scheme makes the set feel disjointed.

Tool Count2/5

With 36 tools, the count is high, but the server name 'Spotify' implies a focused music service. The majority of tools are unrelated to Spotify (e.g., Pipeworx queries, Polymarket bets, dependency scanning), making the tool count feel inflated and inappropriate for the stated domain. A more focused set would be far more coherent.

Completeness1/5

If this is a Spotify server, it is severely incomplete: it lacks playlist management, user actions, and recommendation features beyond top tracks. The inclusion of dozens of unrelated tools (financial data, prediction markets, package analysis) suggests the server has no clear purpose, leaving it neither complete for Spotify nor for any other single domain.

Resources