Skip to main content
Glama

Preview an album

preview_album
Read-onlyIdempotent

Preview any album from Apple Music WITHOUT adding to library. Use this to sample before committing to add. Returns playable 30-second previews.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "artist": "<artist>"
    },
    "name": "preview_album"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesAlbum title
artistYesArtist name
max_tracksNoMaximum tracks to preview (default 5)

Output Schema

NameRequiredDescriptionDefault
artistNo
sourceNo
tracksYes
cover_urlNo
album_titleYes
apple_music_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "description": "Album track list with 30-second preview URLs where available.",
      +  "properties": {
      +    "album_title": {
      +      "type": "string"
      +    },
      +    "apple_music_url": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "artist": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "cover_url": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "tracks": {
      +      "items": {
      +        "additionalProperties": true,
      +        "properties": {
      +          "duration_ms": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          },
      +          "preview_url": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "title": {
      +            "type": "string"
      +          },
      +          "track_number": {
      +            "type": [
      +              "number",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "title"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "required": [
      +    "album_title",
      +    "tracks"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds only that previews are 30 seconds and playable, which is genuine but thin extra context. It says nothing about external-catalog lookup failure, region/availability restrictions, or latency, which the openWorldHint implies but does not explain.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the key constraint ('WITHOUT adding to library') capitalized and front-loaded, so an agent can scan it quickly. The opening phrase marginally restates the tool title, but overall there is very little waste.

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?

The tool is simple (three scalar params, full schema coverage, an output schema, and rich annotations), and the description covers purpose, motivation, and return nature, which is enough to call it correctly. The one remaining gap is behavior when the open-world lookup finds no album or multiple matches, which an agent would have to discover by trial.

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 description coverage is 100%, so title, artist and max_tracks are already documented, and the baseline of 3 applies. The description adds no meaning beyond the schema — it does not say whether title/artist must match the Apple Music catalog exactly, whether max_tracks caps at the album length, or how matching ambiguity is handled.

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 gives a specific verb (preview) plus resource (album) plus source (Apple Music), and the 'WITHOUT adding to library' clause separates it from the many add/add_to_list siblings. It loses a point because the sibling 'get_track_previews' is conceptually adjacent and the description never says whether album-level previews differ from that track-level tool.

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?

'Use this to sample before committing to add' states a clear selection condition relative to the add workflow, which is the main confusion risk in this tool set. It stops short of an explicit exclusion (e.g. 'not for albums already in your library, use get_details/search_library instead'), so it is clear context rather than full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources