Skip to main content
Glama

AutoTasker Hub — China Social Data API

douyin_hot

Douyin (TikTok China) trending word board with hot_value rankings (抖音热榜). $0.02 USDC.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "douyin_hot"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/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. It does add one genuinely useful behavioral fact — the $0.02 USDC cost per call — but it says nothing about the return shape (fields, whether hot_value is numeric or a label), pagination, freshness of the ranking, or failure/rate-limit behavior for a paid endpoint.

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?

A single front-loaded sentence plus a short pricing clause; nothing is redundant or padded. The Chinese parenthetical is useful for matching Chinese-language queries, so it earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read tool with no output schema, the description covers what the tool is and its cost, which is the minimum viable set. It still omits what a response looks like and what hot_value represents, which the agent needs to use results correctly.

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

Parameters2/5

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

Schema description coverage is 0% for the single 'limit' parameter (integer, default 10, max 50). The description never mentions limit, so it adds no meaning beyond the bare type/default constraints, and the maximum of 50 is only discoverable from the schema.

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?

States a specific resource and platform: 'Douyin (TikTok China) trending word board with hot_value rankings'. This is enough for an agent to tell it apart from the other *_hot siblings (baidu_hot, juejin_hot, netease_hot) by platform, though the differentiation is by name only and no explicit comparison is made.

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?

There is no when-to-use or when-not-to-use guidance at all. The agent must infer from 'trending word board' that the tool is for retrieving hot topics, and nothing says how it relates to or differs from the other platform hot-list tools in the catalog.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.