Skip to main content
Glama
Sign In
mcp-applemusic

mcp-applemusic

by suleyman416
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

itunes_seek

Jump to a specific timestamp in the currently playing track by specifying the time in seconds.

Instructions

Seek/jump to a specific timestamp in seconds in the currently playing track.

Args: seconds: Position in seconds from the start of the song.

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": {
      "seconds": "<seconds>"
    },
    "name": "itunes_seek"
  }
}

Input Schema

NameRequiredDescriptionDefault
secondsYes

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?

No annotations are provided, so the description must carry the behavioral disclosure burden. It states the operation (seek/jump) and the target (current track), but does not mention edge cases such as behavior if no track is playing, whether seeking pauses playback, or what happens if seconds exceeds the track length. These gaps are notable but the core behavior is still clear.

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 two sentences plus a parameter list, with the main action front-loaded. No filler words; every line earns its place.

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?

Given the single parameter, no output schema, and straightforward nature of the action, the description is nearly complete. It could mention what happens without a currently playing track, but the essential information for invoking the tool correctly is present.

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?

Schema coverage is 0%, but the description adds essential meaning: 'seconds: Position in seconds from the start of the song.' This fully explains the parameter's semantics beyond the schema's bare integer type.

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 starts with a clear verb and resource: 'Seek/jump to a specific timestamp in seconds in the currently playing track.' It precisely states the action and target, and is clearly distinct from sibling tools like itunes_get_position (read position) or itunes_play (start playback).

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 description implies the tool is used when you want to jump to a timestamp in the current track, and the 'currently playing' qualifier provides useful context. It does not explicitly list when not to use it or name alternatives, but for a simple control action this is sufficient.

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