polylens-bilibili

Overview Schema Source Related Servers Discussions Admin

get_up_info

Read-only

Fetch Bilibili creator profile details—nickname, bio, level, followers, following, likes, verification, and membership—by space URL or mid.

Instructions

含昵称、签名、等级、粉丝数、关注数、总获赞、认证、大会员等。

(uploader profile, channel info, followers)

Input Schema

Name	Required	Description
`jq`	Yes	必填的 jq 表达式。输入是全部条目组成的数组，每条字段：input,mid,author,author_url,sign,sex,level,follower_count,following_count,like_count,official_type,official_title,vip,face_url,error。体积大、多数任务用不到的字段：author_url（给出空间链接时需要）、face_url；特定任务需要时照常使用。每个输入一条，取不到的只有 input 与 error 有值。结果为字符串时原样返回，其他结果编码为表格或 JSON；结果为数组时 jq_count 是其长度。
`authors`	Yes	UP 主列表，每项为空间链接（其他工具返回的 author_url）或数字 mid。
`description`	Yes	格式为工具名:目的。

Output Schema

Name	Required	Description	Default
`count`	Yes
`failed`	Yes
`authors`	Yes
`jq_count`	No
`elapsed_s`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedv0.12.1Oct 14, 2026

removedInput schema / properties / author_url

Removed value: -{
-  "description": "UP 主空间链接（其他工具返回的 author_url），或数字 mid。",
-  "title": "Author Url",
-  "type": "string"
-}

addedInput schema / properties / authors

Added value: +{
+  "description": "UP 主列表，每项为空间链接（其他工具返回的 author_url）或数字 mid。",
+  "items": {
+    "type": "string"
+  },
+  "title": "Authors",
+  "type": "array"
+}

addedInput schema / properties / description

Added value: +{
+  "description": "格式为 工具名:目的。",
+  "title": "Description",
+  "type": "string"
+}

addedInput schema / properties / jq

Added value: +{
+  "description": "必填的 jq 表达式。输入是全部条目组成的数组，每条字段：input,mid,author,author_url,sign,sex,level,follower_count,following_count,like_count,official_type,official_title,vip,face_url,error。体积大、多数任务用不到的字段：author_url（给出空间链接时需要）、face_url；特定任务需要时照常使用。每个输入一条，取不到的只有 input 与 error 有值。结果为字符串时原样返回，其他结果编码为表格或 JSON；结果为数组时 jq_count 是其长度。",
+  "title": "Jq",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "author_url"
-]New value: +[
+  "description",
+  "authors",
+  "jq"
+]

removedOutput schema / properties / author

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Author"
-}

removedOutput schema / properties / author_url

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Author Url"
-}

addedOutput schema / properties / authors

Added value: +{
+  "title": "Authors",
+  "type": "string"
+}

addedOutput schema / properties / count

Added value: +{
+  "title": "Count",
+  "type": "integer"
+}

removedOutput schema / properties / face_url

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Face Url"
-}

addedOutput schema / properties / failed

Added value: +{
+  "title": "Failed",
+  "type": "integer"
+}

removedOutput schema / properties / follower_count

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Follower Count"
-}

removedOutput schema / properties / following_count

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Following Count"
-}

addedOutput schema / properties / jq_count

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Jq Count"
+}

removedOutput schema / properties / level

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Level"
-}

removedOutput schema / properties / like_count

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Like Count"
-}

removedOutput schema / properties / mid

Removed value: -{
-  "title": "Mid",
-  "type": "integer"
-}

removedOutput schema / properties / official_title

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Official Title"
-}

removedOutput schema / properties / official_type

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Official Type"
-}

removedOutput schema / properties / sex

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Sex"
-}

removedOutput schema / properties / sign

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Sign"
-}

removedOutput schema / properties / vip

Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Vip"
-}

changedOutput schema / required

Previous value: -[
-  "mid"
-]New value: +[
+  "count",
+  "failed",
+  "authors"
+]

Changed2 schema fields changedv0.3.1Oct 7, 2026

removedOutput schema / properties / article_count

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Article Count"
-}

removedOutput schema / properties / video_count

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "title": "Video Count"
-}

First observedv0.1.0Oct 5, 2026

TDQS

C2.5/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds nothing behavioral beyond a restatement of returned fields — no note on per-input failure handling (the schema hints that only 'input' and 'error' are populated on failure), no mention that author_url may be omitted to reduce volume, and no error semantics context.

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

Conciseness3/5

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

It is short, which is good, but the content is a field enumeration that largely duplicates the output schema rather than front-loading what the tool does. The second line (the English parenthetical) is the only genuinely informative part, and it is relegated to the end.

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?

An output schema exists, so return values need not be explained — yet the description consists almost entirely of return values. What is missing is the operation itself: that it takes one or more UP masters (space URL or mid) and returns profile data, and why one would call it over sibling tools. For a 3-required-parameter tool, this is inadequate.

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 schema already documents all three parameters (authors, jq, description) thoroughly. The description contributes no additional parameter meaning; baseline 3 applies when the schema carries the full load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name plus the parenthetical '(uploader profile, channel info, followers)' implies fetching uploader profile data, but there is no verb statement — the body is a list of returned fields (nickname, signature, level, follower count, etc.) rather than a description of the operation. No sibling differentiation is offered despite list_up_videos and get_video_info being close relatives. Purpose is inferable but vague.

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 gives no indication of when to use this tool, what it requires (e.g., that it accepts a list of UP masters), or how it differs from list_up_videos or get_video_info. The agent must infer the context entirely from the name.

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

Deploy Server