get_track_previewsGet playable 30-second audio previews for tracks from an album IN THE USER'S LIBRARY.
| Name | Required | Description | Default |
|---|---|---|---|
| max_tracks | No | Maximum tracks to return (default 5) | |
| album_title | Yes | Album title (partial match supported) | |
| track_numbers | No | Specific track numbers (optional) |
| Name | Required | Description | Default |
|---|---|---|---|
| artist | No | ||
| source | No | ||
| tracks | Yes | ||
| cover_url | No | ||
| album_title | Yes | ||
| apple_music_url | No |
Changes observed during successful MCP inspections.
Output 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"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds useful behavioral context beyond the annotations: previews are 30 seconds long, playable, and restricted to albums in the user's library. The annotations already cover read-only, idempotent, non-destructive, and closed-world behavior, so this additional detail is meaningful without needing to repeat safety traits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no wasted words. It immediately states the resource and scope.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the low complexity, rich annotations, full schema coverage, and presence of an output schema, the description is largely complete. The main remaining gap is the absence of explicit usage alternatives, but that is partly covered by the library scoping.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all three parameters are already documented. The description reinforces that album_title must refer to an album in the user's library, but it adds no further parameter semantics beyond what the schema provides. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb+resource: get playable 30-second audio previews for tracks from an album in the user's library. This clearly distinguishes it from general search, but it does not explicitly differentiate it from the sibling tool preview_album.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The only usage constraint is that the album must be in the user's library, which is embedded as a scoping condition rather than guidance. There is no explicit when-to-use or when-not-to-use information, and no alternatives such as preview_album are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.