Skip to main content
Glama

SocialDataX 今日头条 MCP

toutiao_get_hot_search_list

Read-only

读取今日头条热搜榜,返回头条当前热门关键词及上游热度信息。

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": "toutiao_get_hot_search_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
itemsYes普通热搜条目。
pointsYes本次成功调用的积分消耗与账户积分余额。
pinned_itemsYes平台置顶内容。

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedOutput schema / properties / points / description
      Previous value: -"本次成功调用的积分消耗与调用完成时的账户积分余额。"New value: +"本次成功调用的积分消耗与账户积分余额。"
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额,可为负数。"New value: +"优先返回调用完成时查询到的账户积分余额。查询失败时,回退到本次预扣后的余额快照。余额可为负数。"
  2. Changed2 schema fields changed
    • changedOutput schema / properties / points / properties / balance / description
      Previous value: -"本次接口完成时看到的当前积分余额。"New value: +"本次接口完成时看到的当前积分余额,可为负数。"
    • removedOutput schema / properties / points / properties / balance / minimum
      Removed value: -0
  3. Changed16 schema fields changed
    • addedOutput schema / properties / items / items / properties / category / title
      Added value: +"Category"
    • addedOutput schema / properties / items / items / properties / cover_image_url / title
      Added value: +"Cover Image Url"
    • addedOutput schema / properties / items / items / properties / hot_id / title
      Added value: +"Hot Id"
    • addedOutput schema / properties / items / items / properties / hot_value / title
      Added value: +"Hot Value"
    • addedOutput schema / properties / items / items / properties / keyword / title
      Added value: +"Keyword"
    • addedOutput schema / properties / items / items / properties / rank / title
      Added value: +"Rank"
    • addedOutput schema / properties / items / items / properties / tag / title
      Added value: +"Tag"
    • addedOutput schema / properties / items / items / properties / title / title
      Added value: +"Title"
    • addedOutput schema / properties / items / items / properties / url / title
      Added value: +"Url"
    • addedOutput schema / properties / items / items / title
      Added value: +"ToutiaoHotSearchItem"
    • addedOutput schema / properties / items / title
      Added value: +"Items"
    • addedOutput schema / properties / pinned_items / items / properties / title / title
      Added value: +"Title"
    • addedOutput schema / properties / pinned_items / items / properties / url / title
      Added value: +"Url"
    • addedOutput schema / properties / pinned_items / items / title
      Added value: +"ToutiaoPinnedHotItem"
    • addedOutput schema / properties / pinned_items / title
      Added value: +"Pinned Items"
    • addedOutput schema / title
      Added value: +"ToutiaoHotSearchResult"
  4. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so safety and openness are covered. The description adds that results include '上游热度信息' alongside keywords, which is useful content context, but it says nothing about ordering, result count, or refresh cadence for a live ranking endpoint.

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 front-loaded sentence with zero filler: it names the resource first and the returned content second. Nothing is repeated from the name or title.

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 no-argument read tool with an output schema and read-only annotations, the description is sufficient to call it correctly. The only shortfall is the absence of any note on how many items come back or how fresh the ranking is.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No misleading hints about filters or pagination are given.

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 ('读取') and a specific resource ('今日头条热搜榜'), then adds what the payload contains (热门关键词 plus 上游热度信息). None of the siblings cover hot-search data, so an agent can distinguish it, though the description never explicitly says so.

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 only implied: an agent infers this is the tool for trending topics rather than post/user/search queries. There is no explicit when-to-use or when-not-to-use statement, and no mention of a fallback if the list is empty or unavailable.

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.

Resources