Spotify & TMDB Web MCP Server

Overview Schema Source Related Servers Discussions Admin

add_movie_songs_to_playlist

Find songs from a specific movie on Spotify and add them to an existing playlist, with an optional limit on how many tracks to include.

Instructions

Find songs for a specific movie on Spotify and add them directly to an existing playlist.

Args: playlist_id: The Spotify ID of the existing playlist movie_name: Title of the movie max_songs: Maximum number of songs to add (default: 5)

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>",
      "movie_name": "<movie_name>"
    },
    "name": "add_movie_songs_to_playlist"
  }
}

Input Schema

Name	Required	Description	Default
`max_songs`	No
`movie_name`	Yes
`playlist_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Beyond the annotations' mutation, non-idempotent, and open-world signals, the description clarifies that discovery and addition happen directly as one operation. It does not explain soundtrack-matching behavior, duplicate handling, partial failures, or what occurs when fewer than max_songs are found.

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 operation is front-loaded in one clear sentence, followed by a compact and relevant Args block. There is no redundant, promotional, or otherwise unnecessary wording.

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?

Together with the annotations and output schema, the description is sufficient for a basic invocation because the inputs and existing-playlist requirement are clear. For a composite workflow with several closely related siblings, it remains incomplete on tool selection, movie-to-song resolution, duplicates, and partial-success behavior.

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?

With 0% schema description coverage, the Args block provides essential documentation for all three parameters, including the Spotify-specific playlist ID and the meaning of max_songs. Valid ranges and edge-case behavior for max_songs remain unspecified.

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 opening sentence clearly describes a composite operation: finding songs for a specific movie on Spotify and adding them to an existing playlist. It does not explicitly distinguish this workflow from siblings such as fetch_soundtrack_tracks or add_tracks_to_playlist.

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

Usage Guidelines4/5

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

The phrases 'for a specific movie' and 'an existing playlist' establish a concrete use case and target-playlist precondition. However, there is no guidance to use create_playlist when a playlist does not yet exist, fetch_soundtrack_tracks for lookup only, or add_tracks_to_playlist when tracks are already known.

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

Deploy Server