Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

apply_scene

Apply a saved Spotify scene by resolving its device, transferring playback, then setting volume, shuffle, repeat, and starting the saved context in order; missing targets are skipped.

Instructions

Apply a saved scene: resolve its device hint, transfer playback, then set volume/shuffle/repeat and start the saved context (in that order; missing targets are skipped)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesScene name to apply
dry_runNoPreview only: describe what would change without performing it. Default false — pass true to preview.
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 changedv3.0.1
    • addedInput schema / properties / dry_run / default
      Added value: +false
    • changedInput schema / properties / dry_run / description
      Previous value: -"Preview only: validate inputs and describe exactly what would change without performing it"New value: +"Preview only: describe what would change without performing it. Default false — pass true to preview."
  2. Changed2 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv1.26.1

TDQS

A4/5.0
Behavior4/5

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

With only destructiveHint: false in annotations, the description adds meaningful behavioral context: it discloses the multi-step order (resolve device hint, transfer playback, set volume/shuffle/repeat, start context) and that missing targets are skipped. It does not discuss auth needs, reversibility, or rate limits, but it goes beyond the annotation without contradicting it.

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, front-loaded sentence that states the action and execution order without wasted words. Every clause earns its place by conveying the operation or its sequencing.

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 multi-step mutation tool with no output schema, the description is largely sufficient: it covers the execution order and skip behavior for missing targets. It could mention dry-run behavior explicitly, but that is already fully documented in the input schema, so the remaining gap is minor.

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 all three parameters (name, dry_run, response_format) are already fully documented in the schema. The description adds no parameter-level detail beyond what is in the structured input schema, making the baseline of 3 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 states a specific verb ('Apply') and resource ('a saved scene') and immediately distinguishes the operation from siblings like save_scene, list_scenes, and delete_scene. It also spells out the execution sequence, making the tool's scope unambiguous.

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?

Usage is implied: the tool is for applying a saved scene, and the sequence is described. However, there is no explicit guidance on when to choose this over manually calling transfer_playback, set_volume, set_shuffle, set_repeat, or play, nor any exclusion criteria.

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