crates-music-mcp

Overview Schema Source Related Servers Discussions Admin

credential_set_cookie

Import NetEase, QQ Music, and Kugou credentials directly from cookie strings or JSON to authenticate accounts without a login flow.

Instructions

Import a credential blob directly, no login flow needed.

netease: value 是 Cookie 串（MUSIC_U=...; __csrf=...），从浏览器已登录网易云的请求头里整段复制即可。 kugou: value 是 Cookie 串，必须含 token=。 qq_music: value 是完整 Credential JSON（含 musicid / musickey / refresh_key / access_token 等；带 refresh_token 时才能自动续期）。

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": {
      "service": "<service>",
      "value": "<value>"
    },
    "name": "credential_set_cookie"
  }
}

Input Schema

Name	Required	Description	Default
`uid`	No
`value`	Yes
`service`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Nov 9, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations at all, the description carries the full burden and does add real behavior: per-platform value formats and the note that qq_music auto-renews only when refresh_token is present. It omits important traits for a credential write such as whether an existing credential is overwritten, whether the blob is validated immediately, and how failures surface.

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?

Front-loaded one-line purpose followed by a per-platform breakdown, which is exactly the right structure for a format-sensitive parameter. The indented multi-line formatting is slightly noisy but no sentence is filler.

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?

Return values need not be explained since an output schema exists, and the per-platform value formats are covered. However, for a mutation tool with zero annotations, the description should still say what happens to an existing credential, whether uid is required for any platform, and what a rejected blob looks like.

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 0%, so the description must compensate, and it does so for the hardest parameter: it specifies that 'value' is a raw Cookie string for netease, a Cookie string requiring token= for kugou, and a full Credential JSON for qq_music. The 'uid' parameter receives no explanation anywhere, which keeps it from a 5.

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 a specific verb and resource ('Import a credential blob directly') and immediately scopes it against the login flow ('no login flow needed'), which separates it from login_start/login_submit in the sibling set. It does not explicitly name those siblings, so it falls short of a 5.

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?

'No login flow needed' gives a clear routing signal: use this when a cookie/JSON credential already exists rather than starting a login. There is no explicit when-not guidance (e.g., what to do if the blob is stale or invalid, or that credential_refresh should be used afterward), so it stops at 4.

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