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

Spotify & TMDB Web MCP Server

by Chiru144
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

reorder_playlist_by_audio_features

Read-onlyIdempotent

Sorts Spotify playlists by energy, valence, danceability, or tempo; currently leaves them unchanged because Spotify no longer provides these features to Development Mode apps.

Instructions

Unavailable: Spotify no longer provides audio features (energy, valence, danceability, tempo) for Development Mode apps, so playlists cannot be sorted by them. The playlist is left unchanged.

Args: playlist_id: Spotify playlist ID or URI. feature: The audio feature to sort by (e.g., 'energy', 'valence', 'danceability', 'tempo'). order: 'asc' for ascending, 'desc' for descending. ascending: Optional boolean (True for 'asc', False for 'desc'). Overrides order if provided.

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": "reorder_playlist_by_audio_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderNodesc
featureNoenergy
ascendingNo
playlist_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the annotations by explaining the underlying cause (Spotify no longer exposes energy/valence/danceability/tempo for Development Mode apps) and the concrete outcome ('the playlist is left unchanged'). This is consistent with readOnlyHint=true and destructiveHint=false and adds real context a no-op stub would otherwise lack.

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?

The critical fact — unavailability and unchanged playlist — is front-loaded in the first two sentences, followed by a compact args block. Little waste, though the parameter list documents arguments the tool can never honor.

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 non-functional stub, the description supplies everything needed: why it fails, what happens to the playlist, and what each argument means. With an output schema present, no return-value explanation is required.

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

Parameters4/5

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

Schema coverage is 0%, so the description carries the full burden and does so: it defines playlist_id (ID or URI), names example values for feature, gives 'asc'/'desc' for order, and explains that ascending overrides order. It does not clarify the defaults (desc, energy) that appear in the schema, which is the main residual gap.

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 the specific verb and resource (sorting a playlist by audio features) and immediately declares the tool is unavailable, so an agent knows both what it would do and that it cannot be used. It is distinguishable from siblings, though it never explicitly says to use another tool instead.

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 unavailability statement effectively conveys 'do not call this,' which is useful negative guidance. However, no alternative route or sibling tool is named for achieving playlist ordering, leaving the agent to infer next steps on its own.

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