Skip to main content
Glama

Get track previews

get_track_previews
Read-onlyIdempotent

Get playable 30-second audio previews for tracks from an album IN THE USER'S LIBRARY.

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": {
      "album_title": "<album_title>"
    },
    "name": "get_track_previews"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_tracksNoMaximum tracks to return (default 5)
album_titleYesAlbum title (partial match supported)
track_numbersNoSpecific track numbers (optional)

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?

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely new context: previews are 30-second and playable, and the album must be in the user's library. It says nothing about what happens when the album is absent or about rate/availability limits for audio URLs.

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?

A single sentence with the key constraint front-loaded and no filler. Nothing could be removed without losing information.

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?

With a full output schema, rich annotations and complete parameter documentation, the description only needs to state purpose and scope, which it does. The one remaining gap is disambiguation from the closely named sibling 'preview_album'.

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%, with all three parameters documented in the schema, so the baseline of 3 applies. The description adds no field-level meaning such as how track_numbers interacts with max_tracks or what partial matching on album_title accepts.

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?

States a specific verb and resource ('Get playable 30-second audio previews for tracks from an album') plus a scope qualifier ('IN THE USER'S LIBRARY'). It does not, however, distinguish itself from the sibling tool 'preview_album', which an agent could easily confuse with this one.

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 capitalized 'IN THE USER'S LIBRARY' implies the precondition that only library albums yield results, which is useful usage context. There is no explicit when-to-use / when-not-to-use framing and no pointer to 'preview_album' or 'search_library' as alternatives.

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