mcp-spotify

get_multiple_artists

Retrieve Spotify artist details for multiple artists at once by providing their IDs or URIs (up to 50).

Instructions

Get Spotify catalog information for multiple artists

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": {
      "ids": "<ids>"
    },
    "name": "get_multiple_artists"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes	Array of Spotify artist IDs or URIs (max 50)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.4Sep 11, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden but only states what the tool does without behavioral details. It doesn't disclose rate limits, authentication needs, error handling, or response format (e.g., JSON structure), which are critical for an agent to use it effectively in a real-world scenario.

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?

The description is a single, direct sentence with no wasted words, efficiently conveying the core purpose. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly without unnecessary elaboration.

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?

Given the lack of annotations and output schema, the description is incomplete for a tool that likely returns complex artist data. It doesn't explain what 'catalog information' includes (e.g., genres, popularity) or handle potential errors, leaving gaps in understanding the tool's full behavior and output.

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?

The input schema has 100% description coverage, fully documenting the 'ids' parameter with type, format, and max items. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without extra value.

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?

The description clearly states the verb ('Get') and resource ('Spotify catalog information for multiple artists'), making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_artist' or 'get_multiple_albums', which would require mentioning the multi-artist batch capability as a distinguishing feature.

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 is provided on when to use this tool versus alternatives like 'get_artist' for single artists or 'search' for finding artists. The description lacks context about batch efficiency or limitations compared to other artist-related tools, leaving the agent without usage direction.

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