Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bilibili_vertical_home

Fetch stable server-rendered Bilibili home sections for documentary, movie, TV, or variety verticals, returning editorial content by category.

Instructions

Get Bilibili documentary, movie, TV, or variety home sections. Returns stable server-rendered editorial sections for one Bilibili vertical. Allowed category values: documentary, movie, tv, variety. Rotating feeds, pagination, account state, and streaming URLs are excluded.

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": {
      "category": "<category>"
    },
    "name": "bilibili_vertical_home"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesVertical: documentary, movie, tv, variety

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / category / enum
      Added value: +[
+  "documentary",
+  "movie",
+  "tv",
+  "variety"
+]
  2. Addedv1.16.2

TDQS

A4.2/5.0
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 discloses that the output is stable editorial sections and explicitly lists what is excluded (rotating feeds, pagination, account state, streaming URLs). This provides essential behavioral context, though it does not mention read-only nature or return structure.

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 two sentences with zero fluff. The first sentence states purpose and categories; the second lists exclusions. It is front-loaded and every phrase contributes value.

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 one-parameter tool, the description covers the return type (editorial sections), the allowed inputs, and what is excluded. It does not describe the response structure, but without an output schema, this is not critical. The tool is adequately specified for an agent to call it correctly.

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 fully documents the single 'category' parameter with an enum and description ('Vertical: documentary, movie, tv, variety'). The description repeats these allowed values but adds minimal new meaning, just confirming the categories. Since schema coverage is 100%, the baseline 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 the tool's purpose: fetching Bilibili home sections for documentary, movie, TV, or variety categories. It uses a specific verb ('Get') and resource ('home sections'), and the enumerated categories distinguish it from sibling tools like bilibili_anime_home or bilibili_guochuang_home, even without naming them.

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 gives clear context: it returns stable server-rendered editorial sections and explicitly excludes rotating feeds, pagination, account state, and streaming URLs. However, it does not explicitly name alternative tools or state when not to use this tool, though the category list implies the scope.

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