netease-music-mcp

Server Quality Checklist

Profile completionA complete profile improves this server's visibility in search results.

Latest release: v1.0.0
Disambiguation5/5
Each tool targets a distinct resource or action: search, various recommendation feeds, metadata lookups by type, lyrics, library, statistics, and write operations. Potential overlaps like 'get_recommendations' vs 'get_new_songs' are clearly separated by content type and description, leaving no ambiguity.
Naming Consistency4/5
Most tools follow a verb_noun snake_case pattern (get_*, create_*, update_*, set_*), which is highly consistent. The sole exception is 'music_search', which reverses the order (noun_verb) instead of 'search_music', but this is a minor deviation in an otherwise predictable set.
Tool Count5/5
15 tools is well-scoped for a music service, covering search, discovery, metadata retrieval, user library access, statistics, and playlist management. Each tool has a clear and justified place, with no redundant or filler tools.
Completeness4/5
The tool surface covers the core lifecycle: browsing, searching, fetching details, managing playlists, and liking songs. Minor gaps include no delete playlist operation, no user profile endpoint, and limited artist discography, but these are workaroundable and do not severely hinder typical music workflows.
Average 3.7/5 across 15 of 15 tools scored.
See the Tool Scores section below for per-tool breakdowns.
- No community issues in the last 6 months
- 11 commits in the last 12 weeks
- No stable releases found
- No critical vulnerability alerts
- No high-severity vulnerability alerts
- No code scanning findings
- CI is passing
This repository is licensed under MIT License.
This repository includes a README.md file.
No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.
Tip: use the "Try in Browser" feature on the server page to seed initial usage.
Add a glama.json file to provide metadata about your server.
If you are the author, simply .
If the server belongs to an organization, first add glama.json to the root of your repository:
```
{
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}
```
Then . Browse examples.
Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It only discloses that confirmation is required, but omits side effects, reversibility, permission requirements, and error behavior. This is insufficient for a mutation tool.
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 a single concise sentence that immediately states the verb and resource. Every word earns its place, with no filler or redundancy.
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?
Despite complete schema and output schema, the description lacks critical behavioral context for a mutation tool: no mention of required authentication, what happens on failure, or relationship to other playlist/song tools. This is minimally viable at best.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% with clear parameter descriptions for playlist_id, song_ids, operation, and confirm. The description adds no extra meaning beyond the schema, so the baseline score of 3 applies.
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 clearly states a specific action ('Add or remove songs') on a specific resource ('NetEase playlist'), with the additional constraint 'after confirmation.' It is easily distinguishable from sibling tools like create_playlist and set_song_like.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
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 alternatives such as create_playlist or set_song_like. The phrase 'after confirmation' hints at a prerequisite but does not clarify the required flow or exclude other tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description only states that the top songs list is 'bounded' without specifying the limit. It does not explicitly disclose that this is a read-only operation or mention potential limitations like error handling or rate limits.
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 a single clear sentence that front-loads the main purpose and includes the optional behavior without any wasted words. It is appropriately sized and well-structured.
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?
The description covers the core function and the optional top songs feature, and the schema covers parameters. However, it lacks usage context and behavioral caveats, which is noticeable given no annotations. It is adequate for a simple fetch tool but not comprehensive.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already provides descriptions for all three parameters with 100% coverage, including the default behavior of include_top_songs and the meaning of top_song_count. The description does not add additional semantic detail beyond the schema, so it meets the baseline but does not exceed it.
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 uses the specific verb 'Fetch' and identifies the resource as 'artist metadata', clearly distinguishing it from sibling tools like get_album or get_playlist. It also mentions the optional top songs list, giving a complete scope of what the tool does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool vs alternatives such as music_search. The description provides no context about prerequisites, exclusions, or scenarios where this tool is preferred.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the transparency burden. 'Fetch' implies a read-only operation and 'bounded' conveys pagination, which adds useful behavioral context. However, it does not disclose error handling, behavior when translation is unavailable, or side effects, leaving some gaps.
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 a single, front-loaded sentence with no unnecessary words. 'Bounded' efficiently conveys pagination, and the sentence structure is clear. Every word earns its place.
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?
Given the output schema exists and all parameters are fully described, the tool becomes usable, but the description itself is minimal. It lacks usage context, pagination behavior details, and relationship to other tools. The description is minimally complete for a straightforward read operation but leaves room for improvement.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description's mention of 'aligned translation and romanization' loosely maps to include_translation and include_romanization, but the schema already describes these parameters. No additional parameter semantics are provided.
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 uses the specific verb 'Fetch' and clearly identifies the resource as a 'bounded lyric page', which distinguishes it from song search or recommendation tools. Mentioning optional aligned translation and romanization adds further specificity. However, it does not explicitly name alternative tools for comparison.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus siblings like music_search or get_songs. There is no mention of prerequisites, exclusions, or alternative tool names, leaving the agent without clear selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions 'deterministic' but does not disclose whether the operation is read-only, potential performance implications of track_limit, error behavior, or any side effects. This is minimal behavioral disclosure.
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?
A single, tightly worded sentence that front-loads the action and lists key outputs. No redundancy or filler, though it could include a bit more context without becoming verbose.
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?
An output schema exists, so return values are covered elsewhere. The description is missing usage context (when to use vs siblings) and behavioral caveats (e.g., what 'maximum analyzed tracks' means in practice). For a statistics tool, it is adequate but not rich.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Input schema coverage is 100%, so baseline is 3. The description adds no parameter-level meaning beyond the schema; it doesn't even mention the parameters. The schema already provides clear descriptions for playlist_id and track_limit.
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 uses a specific verb ('compute') and resource ('playlist statistics'), and lists concrete statistic dimensions (duration, artist, album, year, availability). This clearly distinguishes it from sibling tools like get_playlist or music_search.
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?
Usage is implied rather than explicit. The description states what the tool computes but gives no guidance on when to prefer it over get_playlist (which might return similar data) or any exclusions/prerequisites. No alternatives are named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the transparency burden. It discloses that results are paginated ('compact paginated results') which is a useful behavioral trait, but it does not mention authentication, rate limits, error handling, or whether the operation is read-only (though 'search' implies non-destructive). It partially covers behavior but lacks depth.
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 a single sentence, front-loaded with the verb and resource, and contains no filler words. Every word adds value, making it highly concise and well-structured.
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 tool's simplicity, the presence of a rich input schema with full descriptions, and an output schema, the description covers the essential purpose and result style (paginated, compact). It doesn't explicitly address when to use it vs. siblings or edge-case behavior, but for a search tool with this schema, it is reasonably complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% with all 5 parameters having descriptions. The description adds minimal parameter-level meaning (e.g., 'compact' relates to detail_level, 'paginated' relates to page/page_size) but the schema already documents the parameters well, so the baseline of 3 is appropriate.
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 clearly states the verb 'search' and the resource domain (songs, artists, albums, playlists) with a scoping detail 'compact paginated results'. It distinguishes from siblings like get_songs or get_album by being a general search, but it doesn't explicitly differentiate or exclude specific use cases.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives like get_recommendations or get_songs. The description doesn't state any prerequisites, exclusions, or when this search is preferred over specific entity retrieval tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that tracks can optionally be included, but does not disclose behavior such as pagination limits, error handling, or authentication requirements. This is minimal for a read operation.
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 a single concise sentence that is front-loaded with the core action. Every word contributes value, with no fluff or repetition.
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?
With an output schema present, return values are covered. However, the description lacks context on when to use track_page or how pagination works, which could affect correct invocation. For a simple fetch tool, it is adequate but not highly informative.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description does not add meaning beyond the schema for parameters like 'album_id' or 'track_page', but the phrase 'optionally one page of tracks' hints at the include_tracks and track_page relationship. This is sufficient given full schema coverage.
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 clearly states the tool's function with a specific verb ('Fetch') and resource ('album metadata'), and mentions the optional inclusion of tracks. This distinguishes it from sibling tools like get_artist or get_playlist by focusing on the album entity.
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 description implies the tool should be used when album metadata is needed, but it does not explicitly state when to use it versus alternatives. No exclusions or alternative tool mentions are provided, leaving the agent to infer usage from the tool's name and description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description says 'Read,' which indicates a non-mutating operation, but this is already implied by the verb 'get' in the tool name. With no annotations provided, the description does not disclose additional behavioral traits such as pagination behavior, authentication requirements, rate limits, or what 'compact' means in terms of response structure. Minimal extra value beyond the verb.
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 a single, front-loaded sentence that immediately states the action and resource. It is concise and every word contributes to understanding the tool's purpose.
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?
The tool is simple with two parameters, both well-described in the schema, and an output schema exists. The description provides the high-level context of retrieving ranking boards with compact top tracks, which is sufficient for a read-only tool. It could benefit from noting whether authentication is needed, but overall the provided information is complete enough for selection.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with clear descriptions for both 'page' and 'page_size'. The description itself does not add semantics beyond what the schema provides, but the schema already handles parameter understanding, so the baseline score of 3 is appropriate.
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 clearly states the tool 'Read a page of NetEase ranking boards with compact top tracks.' It uses a specific verb ('Read') and resource ('NetEase ranking boards'), and the mention of 'compact top tracks' adds useful detail. This distinguishes it from sibling tools like get_songs or get_playlist, which are not about rankings.
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 description implies when to use the tool: when you need NetEase ranking data. However, it does not explicitly state alternatives or provide exclusions, such as 'Use get_recommendations for personalized suggestions instead.' The usage context is clear from the purpose but not elaborated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries the full burden. It only states 'Read' and 'page', which implies a non-mutating operation, but it does not disclose pagination defaults, output format, ordering, or any other behavioral traits such as rate limits or required authentication.
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 a single, front-loaded sentence with no unnecessary words. It conveys the essential purpose efficiently.
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 simple paginated read tool, an output schema is present, and all parameters are fully documented in the schema, the description covers the core purpose. Minor gaps remain about recommendation behavior, but the overall context is adequate.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with each parameter already documented (area, page, page_size). The description adds minimal semantic value beyond 'by region' and 'page', so the baseline of 3 is appropriate.
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 clearly states the verb ('Read'), the resource ('page of recommended new songs'), and the scope ('by region'). This distinguishes it from sibling tools like get_recommendations or get_rankings by emphasizing 'new' songs and region-based filtering.
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 context is clear: use this tool to read region-specific new song recommendations. However, it does not explicitly mention alternatives or when not to use it, though the regional focus implies differentiation from broader recommendation tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of transparency. It discloses that tracks are optional and limited to 'one bounded page,' which is valuable behavioral context. However, it does not mention authentication, rate limits, or explicitly confirm read-only semantics, leaving some ambiguity for a fetch operation.
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 a single, front-loaded sentence with no filler. Every word—'Fetch,' 'playlist metadata,' 'optionally,' 'bounded page'—contributes directly to understanding the tool's behavior.
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 presence of an output schema and the simplicity of a fetch operation, the description covers the essential behavior. It clearly communicates the optional, paginated track retrieval, and the schema handles parameter defaults. It could be slightly more explicit about the default of include_tracks, but that is already in the schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with all four parameters documented individually. The description's phrase 'bounded page of tracks' adds a slight semantic layer by implying pagination and the optional nature of include_tracks, but it does not materially extend what the schema already provides.
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 uses a specific verb 'Fetch' with a clear resource 'playlist metadata' and explicitly mentions an optional track page. This immediately distinguishes it from sibling tools like get_playlist_statistics or get_songs, making the primary purpose unambiguous.
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 description implies usage for fetching playlist metadata but provides no explicit when-to-use or when-not-to-use guidance, nor does it mention alternative tools. It is left to the agent to infer that this is the correct getter for playlist data without any comparative context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the burden. 'Read' indicates a non-destructive operation, which is useful. But it does not disclose error behavior, rate limits, pagination details beyond the word 'page', or whether similar songs are based on current trends vs permanent attributes. No contradiction with 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?
A single, front-loaded sentence with no redundant wording. It states the verb, resource, and target input efficiently, making it easy to scan.
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 read tool with a full input schema and output schema, this description is adequate for invocation. It lacks nuance like sort order, empty-result behavior, or special cases, but these are not critical for basic use. The existence of an output schema reduces the need to describe return values.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with each parameter already documented (song_id, page, page_size). The description adds no extra meaning beyond the schema's own explanations, so the baseline 3 applies.
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?
Description uses specific verb 'Read' with resource 'a page of songs similar to one NetEase song', clearly distinguishing from search/recommendation tools by focusing on song similarity. It immediately tells the agent what the tool does and what its input is.
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?
Implied usage is clear: use when needing songs similar to a specific NetEase song. However, there is no explicit when-to-use vs alternatives, no prerequisites, no exclusion of search or recommendation tools. The guidance is minimal but not misleading.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden, and it does disclose two behavioral traits: it requires authentication ('authenticated') and it is paginated. However, it does not state return formats, error behavior, or whether it is strictly read-only (though 'Read' implies this). More detail would be valuable.
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 a single, well-structured sentence that is front-loaded with the key action and resource. It contains zero wasted words and efficiently conveys the essential purpose.
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?
The output schema is present, so return values are defined. The description gives enough context about the tool's purpose and scope for a simple paginated library reader, though it could mention the available sections (which are in the schema enum) and clarify the intended use case relative to siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so every parameter already has a description in the schema. The tool description does not add additional parameter semantics beyond restating that it is paginated and library-specific, which meets the baseline for high coverage.
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 clearly identifies the verb (Read), the resource (a user's music library), and the scope (authenticated, paginated section). Among siblings, this is the only tool specifically for accessing a user's own library, so it is distinct from search and recommendation tools.
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 phrase 'user's music library' implies it is for retrieving authenticated user content, but there is no explicit guidance about when to use this tool versus alternatives like music_search or get_recommendations. The context is clear enough for a human but not explicitly articulated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of disclosing side effects. It reveals that creation requires explicit confirmation, hinting at a safety mechanism, but it doesn't describe what happens if confirmation is false, or any other behavioral constraints like authentication. It adds some value but lacks depth.
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?
One succinct sentence conveys action and prerequisite without waste. Front-loads the verb 'Create' for immediate understanding.
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?
With full schema coverage and an output schema present, the agent has the necessary parameter details. The description adds the confirmation requirement, making it sufficiently complete for a simple creation tool, though it doesn't discuss return values (covered by output schema) or alternative tools.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema covers 100% of parameters with descriptions, so the baseline is 3. The description's mention of 'explicit confirmation' echoes the confirm parameter's description but doesn't add new meaning to name or private.
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 uses the specific verb 'create' and the resource 'NetEase playlist', clearly distinguishing it from the read-only sibling tools like get_playlist and music_search. It also adds the critical condition 'after explicit confirmation,' which is not present in the tool name.
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 primary use case (creating a playlist) and provides a key usage guideline (must have explicit confirmation). However, it doesn't explicitly name alternatives or say when not to use, but given the sibling list is all read-oriented, the intended use is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses the order-preserving behavior and implies a read-only operation, but it omits details like how invalid IDs are handled, whether partial results are returned, or any rate-limit considerations. This leaves some behavioral ambiguity.
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 a single, focused sentence that front-loads the primary action ('Fetch metadata') and immediately adds the key batch/order traits. No redundant words or information; every word 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 tool's simplicity (2 params, output schema present, no nested objects), the description covers the essential behavior. It doesn't explain error responses or edge cases, but the combination of schema, output schema, and brief description is largely sufficient for an agent to invoke the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, providing baseline semantics for both parameters. The description adds meaning beyond the schema by stating that input order is preserved, which is directly relevant to the song_ids parameter. This extra detail enhances understanding of the main parameter.
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 clearly states the tool fetches metadata for multiple songs in one call, which is a specific verb-resource pair. It also distinguishes from sibling tools by highlighting batch retrieval and order preservation, which other song-related tools (e.g., get_new_songs, get_similar_songs) do not.
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 description implies usage (use when you need metadata for multiple songs) but does not explicitly state when to prefer this over alternatives or provide exclusions. It lacks guidance such as 'for a single song, use get_album' or 'for searching, use music_search', so the agent receives only implicit context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It explicitly labels the operation as 'read-only', indicating non-mutating behavior, and mentions pagination. However, it does not disclose auth requirements, rate limits, or other potential side effects.
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 a single, front-loaded sentence with no fluff. It communicates purpose and key trait (read-only) in 9 words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple paginated read tool with a full output schema, the description sufficiently covers purpose, safety, and pagination. The output schema handles return value details, so no further context is needed.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already provides 100% coverage with descriptions for 'page' and 'page_size'. The tool description ('Read a page') adds no further meaning beyond what the schema already states.
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 clearly states the action ('Read'), resource ('recommended playlists'), and scope ('a page'), distinguishing it from siblings like get_playlist or get_new_songs. The verb is specific and the resource is well-defined.
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 description implies use when browsing NetEase recommendations, but it does not explicitly state when to use it over alternatives or provide exclusions. No sibling tools are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It effectively communicates that the tool mutates like status (like/unlike) and requires explicit confirmation, which is a key safety behavior. It does not detail permissions or error handling, but for a simple mutation tool, the core side effects are disclosed.
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 a single, tightly worded sentence with no filler. It front-loads the action and embeds the key requirement (confirmation) without wasting words.
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 tool's simplicity, an output schema exists, and schema coverage is 100%, the description is nearly complete. It covers the essential behavioral context (confirmation, like/unlike) but omits minor details like authentication or rate limits, which are not critical for this straightforward operation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already provides complete descriptions for all three parameters, giving a baseline of 3. The description adds semantic context by linking 'like or unlike' to the liked parameter and 'explicit confirmation' to the confirm parameter, enriching the meaning beyond the schema alone.
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 clearly states the tool's function: to like or unlike one NetEase song. The verb 'Like or unlike' is specific and the resource 'one NetEase song' is unambiguous, making it distinct from sibling tools like get_user_library or update_playlist_tracks.
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 provides a clear usage condition: the operation should only be performed 'after explicit confirmation'. This conveys when the tool is appropriate to use and implies a prerequisite, though it does not explicitly name alternatives or exclusions. It gives enough context to avoid misuse.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

Confirm that the MCP server is working as expected.
Confirm that there are no obvious security issues.
Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

Copy to your README.md:

[![netease-music-mcp MCP server](https://glama.ai/mcp/servers/YuanYeYouTao/netease-music-mcp/badges/card.svg)](https://glama.ai/mcp/servers/YuanYeYouTao/netease-music-mcp)

Score Badge

Copy to your README.md:

[![netease-music-mcp MCP server](https://glama.ai/mcp/servers/YuanYeYouTao/netease-music-mcp/badges/score.svg)](https://glama.ai/mcp/servers/YuanYeYouTao/netease-music-mcp)

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/YuanYeYouTao/netease-music-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server