Skip to main content
Glama
netease-music-mcp
by xinyu68

netease_song_detail

Read-only

Retrieve song details and lyrics by song ID to inspect track metadata and timestamped lyrics; viewing details does not grant playback permission.

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": {
      "songId": "<songId>"
    },
    "name": "netease_song_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
songIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already establish read-only, non-destructive, open-world behavior, so the burden on the description is lighter. The description then adds a genuinely non-obvious behavioral fact: visibility of details does not imply playback permission, which prevents an agent from treating a successful response as authorization to play. It still omits what happens for invalid or unavailable song IDs.

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?

Two compact clauses, front-loaded with the verb and resource before the caveat. Nothing is padding, though the second clause is terse to the point of being slightly cryptic out of context.

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 one-parameter, non-destructive read tool with annotations and no output schema, the definition covers the essential safety caveat. However, it says nothing about the shape of the returned song info or lyrics, and nothing about how to obtain a valid songId, leaving real gaps for an agent invoking it cold.

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% for the single required parameter, so the description is the only place meaning could be added, yet it never mentions songId at all: no format, no source, and no hint that netease_search is the sibling that supplies it. The regex pattern in the schema is the only clue an agent gets.

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 verb and resource: '读取歌曲信息和歌词' (read song info and lyrics). That is clear enough for an agent to understand the tool's job, but the description does not distinguish this tool from the sibling netease_lyrics, which likely also returns lyrics; the overlap is left for the agent to infer.

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?

There is no explicit when-to-use or when-not-to-use guidance, and the sibling netease_lyrics is never named as an alternative. The caveat '详情可见不代表具有播放权限' hints at a contextual read (metadata inspection is not equal to playback rights), which implies usage without stating it.

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