Weibo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_usersC | |
| get_profileC | |
| get_feedsC | |
| get_hot_feedsC | |
| get_trendingsB | |
| search_contentC | |
| search_topicsC | |
| get_followersC | |
| get_fansC | |
| get_commentsC | |
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 10 tools
Most tools have distinct purposes targeting specific resources like comments, fans, feeds, or searches, but get_feeds and get_hot_feeds could be confused as both retrieve feeds with unclear differentiation in their descriptions. The search tools (content, topics, users) are well-distinguished by their targets.
All tools follow a consistent verb_noun naming pattern (e.g., get_comments, search_users), using snake_case throughout. The naming is predictable and readable, with no deviations in style or convention across the set.
With 10 tools, the count is well-scoped for a Weibo server, covering key social media functions like user profiles, feeds, searches, and interactions. Each tool appears to earn its place without feeling excessive or insufficient for the domain.
The tool set covers read operations (get, search) well but lacks obvious write or update actions like posting, commenting, or following, which are core to social media platforms. This creates notable gaps that agents cannot perform full lifecycle management, though basic retrieval workflows are supported.