Skip to main content
Glama
Sign In
mcp-applemusic

mcp-applemusic

by suleyman416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

itunes_generate_share_link

Generate a song.link universal share link for the current or specified song, enabling sharing across Spotify, YouTube, Tidal, and more.

Instructions

Generate a universal share link (song.link) for friends on Spotify, YouTube, Tidal, etc.

Args: song: Optional track title or 'Title Artist'. If empty, uses currently playing track.

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_generate_share_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
songNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.5

TDQS

A4.3/5.0
Behavior3/5

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

The description discloses that it uses the currently playing track if 'song' is empty, which implies reading current state. However, it does not mention return format, potential network dependencies, or side effects, leaving some ambiguity given no annotations.

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 concise, with two sentences that clearly state purpose and parameter usage without superfluous details.

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 simple tool with a single optional parameter, the description covers the main functionality and usage. It omits specifics about the returned link (e.g., format), but that may be obvious to the user, and no output schema is provided.

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 description adds significant meaning to the 'song' parameter by specifying acceptable formats ('Title' or 'Title Artist') and the behavior when empty, which the schema alone does not convey.

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 explicitly states the tool generates a universal share link for songs, with a clear verb and resource. It distinguishes from sibling tools focused on playback control, playlist management, and other iTunes functions.

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?

It provides context for when to use (sharing to friends on Spotify/Tidal) and explains the optional 'song' parameter behavior. While it doesn't explicitly contrast with alternatives, the unique purpose among siblings makes it clear.

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