AI Social Data MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AISOCIALDATA_MCP_URL | No | Custom service address for the MCP endpoint. Defaults to https://www.aisocialdata.xyz/mcp, but can be overridden for self-hosted or alternative endpoints. | https://www.aisocialdata.xyz/mcp |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_hot_listA | 获取社媒平台当前热点榜或热搜榜。适合回答今日热点、热门话题和实时趋势；不适合按关键词搜索历史内容。 |
| social_searchA | 按关键词搜索抖音公开内容或用户。count 是单页目标；当用户要求的总量超过本页且返回 pagination.has_more=true 时，必须传回 pagination.next_cursor、search_id、search_context 自动继续调用，直到满足用户数量或无更多结果，不能只返回第一页。 |
| get_content_detailB | 获取单条公开内容的详细数据，包括作者、正文和互动指标。传 content_id 或平台分享文案 share_text。 |
| get_user_profileA | 获取公开用户资料。传 user_id、抖音 sec_user_id 或用户分享文案；不要用于获取私密账号数据。 |
| get_user_postsA | 获取公开用户发布内容列表。count 是单页目标；当用户要求更多且返回 pagination.has_more=true 时，必须保持用户参数并用 pagination.next_cursor 自动继续调用，直到满足用户数量或无更多结果。 |
| get_commentsA | 获取公开内容的一级或二级评论。count 是单页数量，抖音最多 30；当用户要求更多且返回 pagination.has_more=true 时，必须保持内容与层级参数，并用 pagination.next_cursor 自动继续调用，直到满足用户数量或无更多结果。抖音一级评论传 content_id，二级评论还需 comment_id；Bilibili 的 content_id 使用详情返回的数字 aid。 |
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 6 tools
Each tool targets a distinct resource and action—hot lists, keyword search, content details, user profiles, user posts, and comments—with no conceptual overlap. Even social_search and get_user_posts differ by keyword-based discovery vs. user-specific listing.
Five of six tools follow the get_<object> pattern, creating a predictable structure. The single exception, social_search, breaks the pattern but remains clear and readable, so a mild deviation.
With 6 tools, the server is well-scoped for social media data retrieval, covering discovery, detail, and user-centric queries without excess or deficiency.
The toolset forms a complete read-only workflow for social media data: hot list for trends, search for discovery, content detail for specific items, user profile and posts for user-centric exploration, and comments for engagement context. No obvious missing operation within this domain.