netease_searchSearch for songs, artists, or keywords on NetEase Cloud Music using an anonymous read-only API. Get matching results with limits and offsets for targeted discovery.
通过 music.163.com 的匿名只读接口搜索歌曲，不读取账号 Cookie。
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| query | Yes | 歌曲、歌手或关键词 | |
| offset | No |
Changes observed during successful MCP inspections.
v0.6.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description explicitly mentions 'anonymous read-only interface' and 'does not read account cookies', reinforcing the readOnlyHint annotation with additional privacy context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single concise sentence covers purpose and key behavioral constraints without unnecessary verbosity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Missing return format or result description, no pagination explanation beyond parameters, and no error or rate-limit context. The absence of an output schema makes this gap more significant.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Only the query parameter is described ('song, artist or keyword'), while limit and offset lack descriptions. Schema coverage is 33%, and the description does not compensate for the missing parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the tool searches songs via a specific interface, with a specific verb 'search' and resource 'songs', distinguishing it from sibling tools like detail or lyrics.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool versus alternative tools. It implies anonymous/read-only usage but does not state when to prefer search over song_detail or playlist operations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.