weibo-hot-search-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| weibo_COOKIE | Yes | Your Weibo cookie for authentication |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| WeiboGetHotSearchC | Get hot search from weibo. |
| WeiboGetHotSearchDetailA | Get hot search detail by word from weibo. Sometimes the word is not found, that's normal. |
| WeiboGetHotSearchCommentByUrlC | Get hot search comment by url from weibo. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool clearly targets a distinct function: listing hot searches, retrieving details for a specific word, and fetching comments for a URL. There is no overlap in purpose, so an agent can easily choose the correct tool.
All tool names follow the same CamelCase pattern with the common prefix 'WeiboGetHotSearch' and a specific suffix indicating the operation (empty, Detail, CommentByUrl). This consistent naming convention makes the set predictable.
Three tools provide a concise, focused surface for the server's stated purpose of accessing Weibo hot searches. This is within the ideal range and each tool contributes a distinct capability without unnecessary bloat.
The tool set covers the core workflow of browsing hot searches: listing them, getting details for a word, and fetching comments via URL. No obvious gaps exist for the narrow domain of hot search consumption.