Skip to main content
Glama

AutoTasker Hub — China Social Data API

baidu_hot

Baidu Top Search realtime board (百度热搜) — mainland-only trend signal, includes pinned item. $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": "baidu_hot"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavioral traits: realtime freshness, mainland-only scope, that a pinned item is included in results, and a per-call price of $0.02 USDC. It does not mention pagination, rate limits, auth/credential needs, or error behavior, so coverage is partial rather than complete.

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?

A single tight sentence that front-loads the source and resource, then adds scope, a caveat about the pinned item, and cost. Every clause carries information; nothing is filler.

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 data is, its recency, geographic restriction, and price, which is the core an agent needs. It leaves the return shape and the meaning of 'limit' unspecified, so it is adequate but not fully complete.

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% and the single 'limit' parameter is undocumented in the schema (only a default of 10 and maximum of 50). The description says nothing about what limit controls or whether the pinned item counts against it, so it fails to compensate for the coverage gap despite this being a one-parameter tool.

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 verb-like resource ('Baidu Top Search realtime board'), gives the native-language name (百度热搜), and identifies the data class (mainland trend signal). This is enough for an agent to distinguish it from the other *_hot siblings such as douyin_hot or netease_hot, though the description does not explicitly contrast them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: fetch trending topics from Baidu. 'Mainland-only trend signal' gives a useful applicability caveat, but there is no explicit when-to-use/when-not guidance or reference to a sibling for other regions or platforms.

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.