Skip to main content
Glama

get_video_info

get_video_info

Retrieve detailed metadata for Bilibili videos using the video ID, including title, uploader, duration, and view statistics.

Instructions

Get detailed information about a Bilibili video

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bvidYes

Implementation Reference

  • src/mcp.ts:73-145 (registration)
    Dynamic registration of all tools, including 'get_video_info', by fetching tool descriptions from remote API and registering them with generic handler and schema.
    const getServer = async () => {
        console.log("getServer start.........")
        if(!isRegistered) {
            try {
                state.isLoading = true;
    
                const res = await fetch('https://mcp.xiaobenyang.com/getMcpDesc?mcpId=' + mcpID, {
                    method: 'GET',
                });
    
                if (!res.ok) {
                    throw new Error(`请求失败:${res.status}`);
                }
    
                const data = await res.json();
                const apiDescList = data.tools;
    
                for (const apiDesc of apiDescList) {
                    let inputSchema = JSON.parse(apiDesc.inputSchema);
                    const zodDict: Record<string, z.ZodTypeAny> = {};
    
                    Object.entries(inputSchema.properties).forEach(([name, propConfig]) => {
                        let zodType;
                        let pt = (propConfig as { type: string }).type;
                        switch (pt) {
                            case 'string':
                                zodType = z.string();
                                break;
                            case 'number':
                                zodType = z.number();
                                break;
                            case 'boolean':
                                zodType = z.boolean();
                                break;
                            case 'integer':
                                zodType = z.int32();
                                break;
                            case 'array':
                                zodType = z.array(z.any());
                                break;
                            case 'object':
                                zodType = z.object(z.any());
                                break;
                            default:
                                zodType = z.any();
                        }
    
                        if (inputSchema.required?.includes(name)) {
                            zodDict[name] = zodType;
                        } else {
                            zodDict[name] = zodType.optional();
                        }
                    });
    
    
                    addToolXiaoBenYangApi(
                        apiDesc.name,
                        apiDesc.description ? apiDesc.description : apiDesc.name,
                        zodDict);
                }
                isRegistered = true;
                state.isLoading = false;
                console.log("state.isLoading: " + state.isLoading)
                return server;
            } catch (error) {
                console.error("getServer 执行失败:", error);
                state.isLoading = false; // 异常时也需要重置加载状态
                throw error; // 抛出错误,让调用方捕获
            }
        } else {
            return server;
        }
    }
  • Core handler logic that proxies the tool call ('get_video_info' as toolName) to the remote API and formats the response.
    const calcXiaoBenYangApi = async function (fullArgs: Record<string, any>) {
        // 发起 POST 请求
        let response = await fetch('https://mcp.xiaobenyang.com/api', {
            method: 'POST',
            headers: {
                'XBY-APIKEY': apiKey,
                'func': fullArgs.toolName,
                'mcpid': mcpID
            },
            body: new URLSearchParams(fullArgs)
        });
        const apiResult = await response.text();
    
        return {
            content: [
                {
                    type: "text",
                    text: apiResult // 将字符串结果放入 content 中
                }
            ]
        } as { [x: string]: unknown; content: [{ type: "text"; text: string }] };
    };
  • Wrapper handler that prepares arguments with toolName ('get_video_info') and calls the core proxy function.
    const handleXiaoBenYangApi = async (args: Record<string, any>, toolName: string) => {
        // 校验aid是否存在
        if (toolName === undefined || toolName === null) {
            throw new Error("缺少必要参数 'aid'");
        }
        // 合并参数
        const fullArgs = {...args, toolName: toolName};
        // 调用API
        return calcXiaoBenYangApi(fullArgs);
    };
  • src/mcp.ts:50-65 (registration)
    Function used to register each tool (including 'get_video_info') with MCP server, providing generic handler.
    const addToolXiaoBenYangApi = function (
        name: string,
        desc: string,
        params: Record<string, ZodType>
    ) {
        server.registerTool(
            name,
            {
                title: name,
                description: desc,
                inputSchema: params,
            }
            ,
            async (args: Record<string, any>) => handleXiaoBenYangApi(args, name)
        )
    };
  • Dynamic construction of input schema (Zod) from remote tool description for each tool including 'get_video_info'.
    let inputSchema = JSON.parse(apiDesc.inputSchema);
    const zodDict: Record<string, z.ZodTypeAny> = {};
    
    Object.entries(inputSchema.properties).forEach(([name, propConfig]) => {
        let zodType;
        let pt = (propConfig as { type: string }).type;
        switch (pt) {
            case 'string':
                zodType = z.string();
                break;
            case 'number':
                zodType = z.number();
                break;
            case 'boolean':
                zodType = z.boolean();
                break;
            case 'integer':
                zodType = z.int32();
                break;
            case 'array':
                zodType = z.array(z.any());
                break;
            case 'object':
                zodType = z.object(z.any());
                break;
            default:
                zodType = z.any();
        }
    
        if (inputSchema.required?.includes(name)) {
            zodDict[name] = zodType;
        } else {
            zodDict[name] = zodType.optional();
        }
    });
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. While 'Get detailed information' implies a read-only operation, it doesn't specify whether this requires authentication, rate limits, what kind of information is returned, or error handling. The description is too vague for a tool with no annotation support.

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, efficient sentence with zero wasted words. It's front-loaded with the core purpose and appropriately sized for a simple tool.

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?

Given no annotations, 0% schema coverage, and no output schema, the description is inadequate. It doesn't explain what 'detailed information' includes, how to interpret the bvid parameter, or any behavioral aspects. For a tool with this complexity and lack of structured support, it should provide more context.

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 0%, so the schema provides no parameter documentation. The description mentions 'Bilibili video' which hints that 'bvid' is a video identifier, but doesn't explain format, examples, or constraints. This adds minimal value beyond the schema, meeting the baseline for low coverage.

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 'Get' and resource 'detailed information about a Bilibili video', making the purpose specific and understandable. It distinguishes from siblings like get_user_info (user-focused) and search_videos (search-focused), though it doesn't explicitly mention this distinction in the text.

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 alternatives like search_videos or get_user_info. It doesn't mention prerequisites, constraints, or typical use cases, leaving the agent to infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

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/xiaobenyang-com/1777316659451907'

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