Get Douyin follower growth rankings by date. Specify category and daily or weekly period to see which accounts gained the most followers.
抖音涨粉榜，查询指定日期的账号涨粉排行
| Name | Required | Description | Default |
|---|---|---|---|
| category | No | 分类 | |
| dateType | No | 日期类型：1=日榜, 2=周榜 | 1 |
| rankDate | Yes | 榜单日期 YYYY-MM-DD |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.0.4Does 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 only restates the query intent and does not disclose sort order, output format, pagination, or behavior when no ranking data exists for the given date.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single efficient sentence with no wasted words, front-loading the ranking concept before the action. It is appropriately concise for a simple query tool, though it sacrifices useful context for brevity.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple three-parameter query where the schema covers 100% of the parameters, the description is minimally adequate. However, there is no output schema, no behavioral context, and no differentiation from sibling Douyin ranking tools, so the overall context remains incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the parameters are already documented in the schema. The description itself adds no parameter meaning beyond what the schema provides, and the vague 'category' field remains vague, but the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('查询') and resource ('抖音涨粉榜', account follower-growth ranking) with a date qualifier. It is clear enough to be distinguished from sibling tools like douyin-daily-hot or douyin-top-account, though it does not explicitly compare itself to any alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given on when to use this tool versus the many other Douyin ranking/surge tools. The only implied context is '指定日期', but there are no exclusions, alternatives, or prerequisites, and no mention of how dateType interacts with the date.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.