toutiao_news
toutiao_newsGet trending news from Toutiao's hot list to monitor current events and popular topics in real-time.
Instructions
实时数据/今日头条热榜
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
toutiao_newsGet trending news from Toutiao's hot list to monitor current events and popular topics in real-time.
实时数据/今日头条热榜
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'real-time data' which implies freshness, but doesn't describe rate limits, authentication needs, data format, update frequency, or what 'hot list' specifically means. The behavioral characteristics are largely unspecified.
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 extremely concise with just two Chinese phrases separated by a slash. Every element earns its place - '实时数据' (real-time data) and '今日头条热榜' (Toutiao hot list) both contribute essential information with zero waste.
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?
Given no annotations, no output schema, and 15 similar sibling tools, the description is incomplete. It doesn't explain what format the hot list returns, how results are structured, what time period 'real-time' covers, or how this differs from other news tools. For a tool in a crowded namespace, more context is needed.
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?
With 0 parameters and 100% schema description coverage, the baseline is 4. The description doesn't need to explain parameters since there are none, and the schema fully documents the empty input structure.
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 '实时数据/今日头条热榜' clearly states what the tool does (provides real-time data/Toutiao hot list) with specific verb+resource. However, it doesn't distinguish from sibling tools that likely provide similar news/hot list functionality from different platforms, so it's not fully differentiated.
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?
The description provides no guidance on when to use this tool versus the 15 sibling news tools. There's no mention of alternatives, exclusions, or specific contexts where Toutiao news would be preferred over other sources like Weibo, Zhihu, or Baidu.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/xiaobenyang-com/1804087353852938'
If you have feedback or need assistance with the MCP directory API, please join our Discord server