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

Spotify & TMDB Web MCP Server

by Chiru144
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_audio_features

Read-onlyIdempotent

Fetches danceability, energy, valence, and tempo for up to 100 Spotify tracks by URI. Note: Spotify no longer supplies these audio features for Development Mode apps.

Instructions

Unavailable: Spotify no longer provides audio features (danceability, energy, valence, tempo) for Development Mode apps.

Args: track_uris: List of Spotify track URIs (max 100).

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": {
      "track_uris": "<track_uris>"
    },
    "name": "get_audio_features"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_urisYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior3/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 the genuinely useful disclosure that Spotify removed this capability for Development Mode apps — context not derivable from structured fields. It stops short of saying what the call returns under this condition, which is the key remaining behavioral question for a stub.

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 availability warning is correctly front-loaded and the whole definition is two short blocks with no filler. The 'Args:' docstring formatting is slightly mechanical but does not cost the reader anything.

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?

An output schema exists, so return-value documentation is not required, but for a deliberately disabled tool the description should state the actual runtime outcome (error vs. empty payload) and point elsewhere. As written, an agent knows the tool is broken but not how it breaks or what to do instead, which is incomplete for this context.

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 coverage is 0%, so the description must carry the parameter burden, and it does partially: it specifies the URI format ('Spotify track URIs') and a max of 100 items, neither of which appears in the schema. It does not explain what happens at or beyond the 100 limit, nor whether the URIs must belong to the same market/context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (Spotify audio features) and enumerates the fields it would return (danceability, energy, valence, tempo), so the intent is recoverable. However, the dominant message is that the tool is unavailable, leaving it unclear whether calling it errors, returns a stub, or returns nothing — an agent cannot tell what the tool actually does today.

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?

The unavailability note implicitly discourages use, which is some guidance, but it names no alternative — notably the sibling reorder_playlist_by_audio_features is not mentioned, nor is any workaround suggested. There are no explicit when-to-use or when-not-to-use conditions beyond the blanket unavailability statement.

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