Skip to main content
Glama
if530770

redfox-mcp-server

by if530770

trending-hub

Query aggregated hot topics from social platforms by filtering with platform, keywords, and date range. Track viral content across Douyin, Xiaohongshu, Weibo, and more.

Instructions

全网热点聚合查询,按平台和关键词获取热门话题

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endDateNo结束日期 YYYY-MM-DD
keywordsNo关键词(逗号分隔)
platformNo平台:douyin/xiaohongshu/weibo 等douyin
startDateNo起始日期 YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv1.0.4

TDQS

C2.9/5.0
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 implies a read-only aggregation query, but it does not describe return shape, default behavior when no parameters are supplied, whether date ranges are required, or any operational constraints. This is minimal and insufficiently transparent.

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 a single, front-loaded sentence with no filler. There is slight redundancy between '热点' and '热门话题', but overall it is compact and scannable.

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 no annotations, no output schema, and many closely related siblings, the description is too thin. It omits expected output format, default behavior, differentiation from hot-topic alternatives, and operational caveats. Parameter documentation is complete, but that alone does not make the tool contextually complete.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description's mention of platform and keywords reinforces the schema but adds no new semantic detail beyond what each parameter already documents.

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 a query/retrieval operation ('查询'/'获取') applied to a resource ('全网热点'/'热门话题') with explicit filters ('平台和关键词'). It is clear enough to distinguish from platform-specific hot-topic tools, but it does not explicitly differentiate itself from closely related siblings like trending-hub-top10.

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?

No guidance is provided about when to prefer this tool over alternatives such as trending-hub-top10, douyin-daily-hot, or weibo-hot-search. It does not state exclusions, prerequisites, or typical use cases, which is a notable gap given the large set of sibling tools.

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/if530770/redfox-mcp'

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