netease-music-mcp

by xinyu68

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

netease_seek

Seek to a specific second in the current song and keep playback paused if it was paused before seeking.

Instructions

定位到歌曲中的秒数；暂停状态定位后仍保持暂停

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>",
      "requestId": "<requestId>"
    },
    "name": "netease_seek"
  }
}

Input Schema

Name	Required	Description	Default
`seconds`	Yes
`requestId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.6.1Oct 31, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already indicate this is a non-read-only, non-destructive, open-world operation. The description adds a useful behavioral detail: seeking while paused leaves playback paused. It does not cover error cases, track-state prerequisites, or response behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short clauses with no wasted text and the core action is front-loaded. It is concise, though its brevity contributes to missing parameter and behavioral detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a playback-control mutation with two required parameters, no schema descriptions, and no output schema, the definition is too sparse. It omits requestId semantics, error conditions, and any indication of what a successful seek returns.

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

Parameters2/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 explains 'seconds' as a position in the song, but gives no format or range guidance, and does not explain the required 'requestId' parameter at all.

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 states a specific playback action: seeking to a given second within a song. It is clear and distinct from siblings like play, pause, and resume, though it does not explicitly name or contrast those alternatives.

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 paused-state note implies the tool is for changing playback position without changing play/pause state. However, it does not explicitly state when to use this instead of play/resume or what happens if no track is active.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.