Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

playlist_era_profile

Analyzes a playlist's release eras, returning a decade histogram, median track age, and a time-capsule verdict to characterize its vintage.

Instructions

Local release-era profile: decade histogram, median track age, and a time-capsule verdict. Pairs with playlist_era slices. Quota: 🟢 1 GET (market refetch disclosed).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
marketNoISO 3166-1 alpha-2 market, e.g. 'US' — when given, items are REFETCHED with this market so album release dates resolve (disclosed second GET)
dry_runNoPreview only: validate inputs and describe exactly what would change without performing it
max_resultsNoMax items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)
playlist_idYesPlaylist to profile (ID or spotify:playlist: URI)
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.28.0
    • changedInput schema / properties / market / description
      Previous value: -"ISO 3166-1 alpha-2 market. When given, items are REFETCHED with this market so album release dates resolve (disclosed second GET)."New value: +"ISO 3166-1 alpha-2 market, e.g. 'US' — when given, items are REFETCHED with this market so album release dates resolve (disclosed second GET)"
    • addedInput schema / properties / market / pattern
      Added value: +"^[A-Za-z]{2}$"
  2. Addedv1.26.1

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the transparency burden and does well by disclosing the quota ('1 GET') and the market-triggered refetch as a second GET. This is meaningful behavioral context beyond the name and schema, though it does not fully describe output or error behavior.

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?

Two compact sentences front-load the tool's purpose and output components, then add quota and refetch disclosure. Every word earns its place with no filler.

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

Completeness3/5

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

The tool has no output schema and no annotations, so the description needs to carry more of the context. It names the output components and quota, but leaves usage conditions and some response-format nuance to the schema. Adequate for selection, but an agent would still need to infer several operational details.

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%, so the schema already documents all five parameters. The description adds no new parameter-level semantics beyond reiterating the market refetch, which is already in the schema. Baseline 3 is appropriate.

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

Purpose5/5

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

The description names a concrete object ('release-era profile') and specifies its outputs: decade histogram, median track age, and a time-capsule verdict. It also distinguishes itself by being 'local' and by pairing with playlist_era slices, making its role clear among many sibling era/report tools.

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 description implies a playlist-scoped, release-era analysis use case and names a companion ('Pairs with playlist_era slices'), which gives some context. However, it does not explicitly state when to use this tool over sibling era/profile tools or when not to use it.

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