Skip to main content
Glama
Sign In
mcp-applemusic

mcp-applemusic

by suleyman416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

itunes_set_shuffle_mode

Set shuffle granularity to songs, albums, or groupings to control how Apple Music shuffles your library.

Instructions

Set shuffle granularity mode.

Args: mode: 'songs' (shuffle individual tracks), 'albums' (shuffle albums), or 'groupings' (shuffle groupings).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "itunes_set_shuffle_mode"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNosongs

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations available, the description carries the full transparency burden. It explains what the modes mean but does not disclose whether shuffle must already be enabled, whether this call turns shuffle on, how it interacts with current playback, or what the result of the operation is.

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 compact, front-loaded with the action, and avoids filler. The Args block is immediately useful and each sentence earns its place.

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?

For a simple one-parameter setter, the mode definitions make invocation straightforward. However, the absence of any behavioral context—such as prerequisites, side effects, or relationship to shuffle state—leaves notable gaps given there are no annotations and no output schema to clarify behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only provides a default value with no enum or descriptions, while the description fully compensates by listing each allowed mode ('songs', 'albums', 'groupings') with a clear explanation of its behavior. This is exactly the semantic value needed beyond the schema.

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 identifies the action ('Set shuffle granularity mode') and the resource being controlled. It stops short of explicitly distinguishing itself from sibling playback-mode tools like itunes_repeat, though 'shuffle' makes the scope reasonably clear.

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, nor are any prerequisites or exclusions mentioned. The description defines the mode values but never says when shuffle granularity should be configured.

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