Skip to main content
Glama

AutoTasker Hub — China Social Data API

get_hotlist

Trending posts from Chinese social media (Weibo Hot Search, Douban, Zhihu, Bilibili, Tieba). $0.05 USDC per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "board": "<board>"
    },
    "name": "get_hotlist"
  }
}

Input Schema

NameRequiredDescriptionDefault
boardYesBoard: weiboHot | douban | zhihu | bilibili | tieba
limitNoItems to return (max 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are supplied, so the description carries the full burden. It does disclose two genuinely useful behavioral facts beyond the schema: the concrete upstream sources and a per-call price of $0.05 USDC, which lets an agent reason about cost. It says nothing about result freshness, caching, rate limits, or what a returned item looks like, so the safety/behavior profile remains thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences — what it returns and what it costs — with the resource named first. No filler, no restatement of the tool name.

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

Completeness4/5

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

For a 2-parameter read tool with no annotations and no output schema, the description covers purpose, sources, and pricing, which is most of what an agent needs to call it. The remaining gap is return shape: an agent cannot tell what fields each trending item contains (rank, title, heat, URL) or whether results are aggregated across all boards or filtered by the single `board` value.

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%: `board` lists its allowed values and `limit` documents default 10 and max 20. The description's platform names add human-readable meaning to the board values but no format, ordering, or truncation semantics beyond the schema, so baseline 3 applies.

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 gives a specific verb+resource pair ('Trending posts from Chinese social media') and enumerates the covered boards (Weibo Hot Search, Douban, Zhihu, Bilibili, Tieba), which maps directly to the required `board` parameter. It does not, however, distinguish itself from similar siblings such as baidu_hot or douyin_hot, leaving the agent to guess which hot-list source to pick.

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 — no statement about when this is preferable to other trending/hot-search tools in the catalog. The only usage-adjacent signal an agent can infer is the board enumeration.

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.