Skip to main content
Glama

get-juejin-article-rank

get-juejin-article-rank

Retrieve ranked technical articles from Juejin platform across categories like frontend development, backend technology, AI, mobile development, and technical architecture to discover high-quality Chinese technical content.

Instructions

获取掘金文章榜,包含前端开发、后端技术、人工智能、移动开发及技术架构等领域的高质量中文技术文章和教程

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
category_idNo

Implementation Reference

  • Core proxy function that executes the tool logic by making a POST request to the remote API endpoint 'https://mcp.xiaobenyang.com/api' with the tool name in the 'func' header and arguments in the body. This handles all dynamic tools including 'get-juejin-article-rank'.
    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 function called by the registered tool handler, adds toolName to args and invokes 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)
    Helper function that registers each dynamic tool on the MCP server, specifying name, description, input schema, and the proxy handler lambda.
    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)
        )
    };
  • src/mcp.ts:90-132 (registration)
    Dynamic registration loop: fetches tool descriptions from remote API for mcpID '1777316659328003', builds Zod input schemas, and registers each tool (including 'get-juejin-article-rank' if present in the remote list) using addToolXiaoBenYangApi.
    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);
    }
  • Dynamic schema generation: converts JSON schema properties from remote tool descriptions into Zod types for input validation, handling required/optional fields.
    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. It mentions the tool retrieves rankings of '高质量中文技术文章和教程' (high-quality Chinese technical articles and tutorials), which implies a read-only operation, but doesn't specify whether it requires authentication, rate limits, pagination, freshness of data, or what the output format looks like. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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?

The description is appropriately concise with a single sentence that front-loads the core purpose ('获取掘金文章榜' - get Juejin article rankings). It efficiently adds context about content types and domains without unnecessary elaboration. However, it could be slightly more structured by separating purpose from details.

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 the tool's complexity (1 parameter, no annotations, no output schema), the description is incomplete. It covers the purpose and content scope but misses critical details: parameter usage, behavioral traits (e.g., authentication needs, rate limits), and output expectations. For a tool with no structured support, the description should provide more comprehensive guidance to be fully helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one parameter ('category_id') with 0% description coverage, and the tool description provides no information about parameters. The description doesn't mention what 'category_id' is, how to use it, or whether it's optional/required. With low schema coverage, the description fails to compensate, leaving the parameter undocumented.

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 tool's purpose: '获取掘金文章榜' (get Juejin article rankings) with specific resources mentioned ('高质量中文技术文章和教程' - high-quality Chinese technical articles and tutorials) and domains covered ('前端开发、后端技术、人工智能、移动开发及技术架构等领域' - front-end development, back-end technology, AI, mobile development, and technical architecture). It distinguishes from siblings by specifying Juejin as the source, but doesn't explicitly contrast with similar tools like 'get-zhihu-trending' which might also provide Chinese content.

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. It doesn't mention when to choose Juejin articles over other sources like Zhihu or Weibo trending, nor does it specify prerequisites, timing considerations, or exclusions. The context is implied (getting Chinese technical articles from Juejin), but lacks explicit usage instructions.

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/1777316659328003'

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