Skip to main content
Glama
Sign In
mcp-applemusic

mcp-applemusic

by suleyman416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

itunes_set_playlist_description

Update a playlist's description text in Apple Music by specifying the playlist name and new description, ensuring your library's metadata stays current.

Instructions

Set or update the description text on a playlist.

Args: playlist: The name of the playlist. description: Description text for the playlist.

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": "<playlist>",
      "description": "<description>"
    },
    "name": "itunes_set_playlist_description"
  }
}

Input Schema

NameRequiredDescriptionDefault
playlistYes
descriptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the action (set/update) but does not mention side effects, whether the playlist must exist, overwrite behavior, failure modes, or any permissions needed.

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 and front-loaded with a clear one-sentence purpose, followed by a short Args list. Every sentence adds value, and there is no redundancy.

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 setter tool, the basic purpose is clear. However, there is no output schema and no annotations, so the description should clarify result/error behavior (e.g., does it create the playlist if missing? what happens on failure?). This gap leaves the agent uncertain in edge cases.

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?

Schema description coverage is 0%, so the description must compensate. It defines 'playlist' as the name of the playlist and 'description' as the description text, adding meaning beyond the bare schema titles. It does not provide additional format constraints, but for two simple strings this is adequate.

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 clearly states the tool's purpose: 'Set or update the description text on a playlist.' This uses a specific verb and resource, and it is distinct from sibling tools that create, delete, or list playlists.

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?

The usage is implied by the description and name, but there is no explicit guidance on when to use this tool versus alternatives like create_playlist or edit_track_metadata. No exclusions or alternative tool mentions.

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