Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

check_following_artists

Verify which Spotify artists you follow by passing up to 50 artist IDs. Returns a boolean per artist to clarify follow status versus library-saved status.

Instructions

Check if the user follows specific artists — this tests FOLLOW state, not library-saved state (for that use check_in_library). Rows carry {id, uri, follows}; returns a boolean per ID. Max 50.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesSpotify artist IDs to check
max_resultsNoMax items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)
response_formatNo'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API objectconcise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.26.1
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / max_results
      Added value: +{
+  "description": "Max items to return (default: SPOTIFY_MCP_MAX_ITEMS env or 50)",
+  "exclusiveMinimum": 0,
+  "maximum": 2000,
+  "type": "integer"
+}
    • addedInput schema / properties / response_format
      Added value: +{
+  "default": "concise",
+  "description": "'concise' = human prose, 'detailed' = more fields in prose, 'json' = raw API object",
+  "enum": [
+    "concise",
+    "detailed",
+    "json"
+  ],
+  "type": "string"
+}
  2. First observedv1.0.1

TDQS

A4.4/5.0
Behavior4/5

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

There are no annotations, so the description carries the burden. It discloses the row shape ({id, uri, follows}), the boolean-per-ID return behavior, and the 50-item maximum. It does not mention error behavior or auth requirements, but for a simple read-only check the disclosed behavior is substantive.

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 tight sentences with no filler. The core purpose is front-loaded, the distinguishing contrast with check_in_library is immediate, and the return format and limit are stated efficiently.

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

Completeness4/5

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

For a simple check tool with no output schema, the description adequately covers input scope, output shape, and the limit. It could add a note on invalid IDs or the effect of response_format, but the schema already documents response_format and the essential caller needs are met.

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 ids, max_results, and response_format. The description adds a useful clarification that ids are capped at 50 and that the result is boolean per ID, but it does not need to repeat schema-level parameter details.

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 states a specific verb and resource: 'Check if the user follows specific artists.' It also explicitly distinguishes this from library-saved state by naming the sibling alternative check_in_library, making the tool's purpose unambiguous relative to similar tools.

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

Usage Guidelines5/5

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

The description explicitly says this tests FOLLOW state, not library-saved state, and points to check_in_library for the library case. This gives clear when-to-use and when-not-to-use guidance, plus a hard cap of 50 IDs.

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