Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

bilibili_user

Retrieve a public Bilibili profile card by numeric user ID to look up account details and identity information.

Instructions

bilibili: User profile. GET /v1/bilibili/user. Public profile card for a numeric user id. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "mid": "<mid>"
    },
    "name": "bilibili_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
midYesNumeric user id.
cache_max_ageNoServe a cached response when it is newer than this. A cache hit costs 0 credits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the credit accounting in unusual detail: success costs 1 credit, while errors, blocked/timed-out requests, invalid requests and cache hits are free. It says nothing about authentication needs, rate limits, or what the returned profile card actually contains.

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?

Purpose and endpoint are front-loaded in the first two short sentences, with cost information following. The final sentence about not-found/empty-result charging is convoluted and edge-case heavy, slightly diluting the otherwise tight structure.

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 simple two-parameter read tool with no annotations, the description covers purpose and cost well. However, with no output schema it should say more about what the profile card returns, and it omits any mention of auth or throttling, leaving real gaps for an agent.

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 coverage is 100%, so both parameters are already documented in the schema, including 'Numeric user id' and the zero-credit cache hit behavior. The description adds the 'numeric user id' framing but no syntax, format, or usage detail beyond the schema, so the baseline 3 applies.

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 gives a specific verb and resource: it returns a 'Public profile card for a numeric user id' via GET /v1/bilibili/user. The bilibili prefix plus 'user profile' clearly separates it from the other platform user tools in the sibling list, though it never explicitly contrasts with an alternative.

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 stated: an agent can infer it should call this to look up a user by numeric id, and the cost model hints at caching strategy via cache_max_age. There is no explicit when-to-use versus when-not, and no statement of prerequisites or alternatives.

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

Deploy Server

Other Tools