Skip to main content
Glama
LokerL

DouYuSearcher MCP Server

by LokerL
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

DouYuSearcher MCP Server

Python License Status

一个轻量级的 MCP 服务器，支持通过斗鱼房间ID或关键词搜索获取斗鱼直播房间信息。

功能特性

  • 房间信息查询：通过 get_room(room_id) 工具，输入斗鱼房间ID，获取详细房间信息（包括头像、分区、主播、状态、热度等）。

  • 关键词搜索房间：通过 search_rooms(keyword) 工具，输入关键词，搜索相关斗鱼房间。

  • Markdown 表格输出：所有信息均以美观的 Markdown 表格形式返回，支持图片展示。 image

Related MCP server: tinyfish-search-fetch-mcp

安装方法

前置条件

  • Python 3.10+

  • pip

安装步骤

  1. 克隆本仓库：

    git clone https://github.com/LokerL/douyu-mcp-py.git
cd douyu-mcp-py

  2. 安装依赖：

    uv install

使用方法

运行和测试

  • Windows下直接运行：

    ./inspector.cmd

工具说明

工具：get_room(room_id)

根据斗鱼房间ID获取房间详细信息。

  • 参数：room_id（整数，斗鱼房间ID）

  • 返回：Markdown 表格，包含头像、房间ID、分区名、房间名、主播名、房间状态、热度、房间封面图、房间链接。

  • 示例输出：

    | 名称          | 信息             |
|----------------|-------------------|
| 头像           | ![Avatar](https://example.com/avatar.jpg) |
| 房间ID         | 12345   |
| 分区名         | 英雄联盟 |
| 房间名         | 斗鱼最强 |
| 主播名         | 张三 |
| 房间状态       | 直播中 |
| 热度           | 123456 |
| 房间封面图     | ![Room Thumb](https://example.com/thumb.jpg) |
| 房间链接       | [Link](https://www.douyu.com/71415) |

工具：search_rooms(keyword)

通过关键词搜索斗鱼房间，返回第一个相关房间信息。

  • 参数：keyword（字符串，搜索关键词）

  • 返回：Markdown 表格，包含分区名、是否直播、关键词、主播昵称、房间ID。

  • 示例输出：

    | 名称          | 信息             |
|----------------|-------------------|
| 分区名         | 英雄联盟 |
| 是否直播       | 直播中 |
| 关键词         | 英雄联盟 |
| 主播昵称       | 张三 |
| 房间 ID       | 123456 |

许可证

MIT License. 详见 LICENSE。

Available Tools

2 tools
get_roomA
通过斗鱼房间的ID获取斗鱼房间信息。
Get room information from DouYu by room ID.

Args:
    room_id (int): 斗鱼房间ID。整数类型的ID被接受。
    room_id (int): The ID of the DouYu room. A numeric  ID is accepted. Like 71415.

Returns:
    一个markdown表格，包含房间信息。
    a Markdown table containing room information.
    - 头像 URL 使用 image标签展示
    - 房间ID
    - 分区名
    - 房间名
    - 主播名
    - 房间状态（直播中 or 未开播）
    - 热度
    - 房间封面图 URL 图片 使用 image标签展示
ParametersJSON Schema
NameRequiredDescriptionDefault
room_idYes

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the return format (Markdown table with specific fields) and hints at output behavior (image tags for URLs), but does not cover error handling, rate limits, authentication needs, or data freshness. It adequately explains what the tool does but lacks operational details.

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 well-structured with bilingual sections for Args and Returns, making it easy to parse. It is front-loaded with the core purpose and avoids unnecessary details. However, the bilingual duplication slightly reduces efficiency, though it remains concise overall.

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?

Given the tool's low complexity (1 parameter, no annotations, no output schema), the description is largely complete. It explains the purpose, parameter, and return format in detail. Minor gaps include lack of error handling or performance notes, but for a simple read operation, this is sufficient.

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

Parameters5/5

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

The schema description coverage is 0%, so the description must fully compensate. It provides clear semantics for the single parameter 'room_id,' including its type (int), purpose (DouYu room ID), and an example (71415), adding significant value beyond the bare schema. No other parameters exist, making this comprehensive.

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 specific action ('get room information') and resource ('DouYu room'), distinguishing it from the sibling tool 'search_rooms' which likely searches for rooms rather than retrieving by ID. The bilingual format reinforces the purpose without redundancy.

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 implies usage by specifying 'by room ID,' which differentiates it from the sibling 'search_rooms' (suggesting search-based retrieval). However, it lacks explicit guidance on when to use this tool versus alternatives or any prerequisites, such as valid ID ranges or error cases.

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

search_roomsA
通过关键字搜索斗鱼房间。
Search for DouYu rooms by keyword.

Args:
    keyword (str): 查询关键词。
    keyword (str): The search keyword.

Returns:
    一个markdown表格，包含房间信息。
    a Markdown table containing room information.
    - 分区名
    - 是否直播（'直播中' or '未开播'）
    - 关键词
    - 主播昵称
    - 房间 ID
ParametersJSON Schema
NameRequiredDescriptionDefault
keywordYes

TDQS

A4.2/5.0
Behavior3/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. It discloses the return format (a Markdown table with specific fields) and that it searches rooms, which is useful. However, it lacks details on behavioral traits like rate limits, authentication needs, or error handling, leaving gaps in transparency for a search operation.

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 sized and front-loaded with the core purpose, followed by structured sections for args and returns. The bilingual repetition adds some redundancy, but each sentence earns its place by reinforcing clarity without unnecessary fluff.

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?

Given the tool's low complexity (1 parameter, no annotations, no output schema), the description is mostly complete: it explains the purpose, parameter, and return format. However, it lacks details on behavioral aspects like search limitations or result ordering, slightly reducing completeness for a search tool.

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

Parameters5/5

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

With 0% schema description coverage, the description fully compensates by explaining the 'keyword' parameter in both Chinese and English, clarifying its purpose as a search query. This adds essential meaning beyond the minimal schema, making it highly effective for parameter understanding.

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 specific action ('search for DouYu rooms by keyword') and resource ('DouYu rooms'), distinguishing it from the sibling tool 'get_room' which likely retrieves a specific room rather than searching. The bilingual format reinforces the purpose without redundancy.

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 implies usage context by specifying 'by keyword,' suggesting this tool is for finding rooms based on search terms rather than direct lookup. However, it does not explicitly state when to use this versus 'get_room' or provide any exclusions or alternatives, keeping it at a 4.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv0.1.0
    • First observedget_room
    • First observedsearch_rooms
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: get_room retrieves detailed information for a specific room by ID, while search_rooms finds multiple rooms by keyword with summary information. There is no overlap in functionality or ambiguity about when to use each tool.

Naming Consistency5/5

Both tools follow a consistent verb_noun naming pattern (get_room, search_rooms) using snake_case. The naming is predictable and follows the same convention throughout the tool set.

Tool Count2/5

With only 2 tools, this server feels underpowered for a comprehensive DouYu search/seamless experience. While the tools cover basic lookup and search, the domain suggests additional operations like filtering by category, trending rooms, or user profiles would be expected for a complete surface.

Completeness2/5

The tool surface is severely incomplete for a DouYu search domain. There are significant gaps: no ability to browse categories/partitions, get trending/hot rooms, filter search results, or access user/profile information. Agents will hit dead ends when trying to perform common exploration tasks beyond basic ID lookup and keyword search.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • tinyfish-search-fetch-mcp

    dummie21
    A
    license
    A
    quality
    C
    maintenance
    A lightweight MCP server enabling web search and content fetching via TinyFish Free Access API with support for single and burst URL fetch.
    3
    MIT

  • qq-mcp-server

    print-yuhuan
    A
    license
    Not graded
    quality
    D
    maintenance
    A MCP server that exposes QQ bot capabilities over Streamable HTTP, enabling clients to query bot status, read group and friend info, fetch chat history, and send group/private text messages.
    2
    MIT

  • serp-it

    luka-dev
    A
    license
    Not graded
    quality
    C
    maintenance
    An MCP server that aggregates web search results from multiple engines and optionally renders pages to Markdown, providing a unified search interface.
    7 npm
    3
    ISC