Skip to main content
Glama
Sign In
Spotify & TMDB Web MCP Server

Spotify & TMDB Web MCP Server

by Chiru144
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_playlist_tracks

Read-onlyIdempotent

Retrieve the tracks in a specified playlist, with limit and offset controls for paging through results. Use it to inspect or export playlist contents.

Instructions

Get the tracks currently inside a specific playlist.

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": {
      "playlist_id": "<playlist_id>"
    },
    "name": "get_playlist_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
playlist_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds only the word 'currently', hinting at live state, and says nothing about pagination behavior, ordering, or empty results despite limit/offset parameters existing.

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?

A single front-loaded sentence with no wasted words. Brevity is appropriate for a simple read, though it tips into under-specification rather than tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists so return values needn't be explained. However, with 0% parameter coverage and a paged read, the agent is missing paging guidance and any hint about ordering or playlist_id format, which the description should have supplied.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, and the description provides no compensating meaning. limit and offset have defaults but no stated units, maximums, or paging semantics; playlist_id's expected format (ID vs URI) is left ambiguous.

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+resource: fetch tracks belonging to one playlist. It implicitly contrasts with siblings like add_tracks_to_playlist and get_user_playlists, though it never names them. An agent can tell what it retrieves, just not exactly how it differs from fetch_soundtrack_tracks or similar list readers.

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

Usage Guidelines2/5

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

No guidance on when to use this versus get_user_playlists (list playlists) or fetch_soundtrack_tracks. No prerequisites such as needing a valid playlist_id or owning the playlist. The agent must infer all selection logic from the name.

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

Deploy Server

Other Tools