Skip to main content
Glama
YangLang116

TrendRadar

by YangLang116

get_latest_news

Retrieve current news from multiple social platforms. Returns JSON list; adjust limit and include URL as needed.

Instructions

获取最新一批爬取的新闻数据,快速了解当前热点

Args: platforms: 平台ID列表,如 ['zhihu', 'weibo', 'douyin'] - 不指定时:使用 config.yaml 中配置的所有平台 - 支持的平台来自 config/config.yaml 的 platforms 配置 - 每个平台都有对应的name字段(如"知乎"、"微博"),方便AI识别 limit: 返回条数限制,默认50,最大1000 注意:实际返回数量可能少于请求值,取决于当前可用的新闻总数 include_url: 是否包含URL链接,默认False(节省token)

Returns: JSON格式的新闻列表

重要:数据展示建议 本工具会返回完整的新闻列表(通常50条)给你。但请注意:

  • 工具返回:完整的50条数据 ✅

  • 建议展示:向用户展示全部数据,除非用户明确要求总结

  • 用户期望:用户可能需要完整数据,请谨慎总结

何时可以总结

  • 用户明确说"给我总结一下"或"挑重点说"

  • 数据量超过100条时,可先展示部分并询问是否查看全部

注意:如果用户询问"为什么只显示了部分",说明他们需要完整数据

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformsNo
limitNo
include_urlNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/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 discloses that the tool returns a list of news, with optional platform filtering, limit (default 50, max 1000, actual may be less), and include_url. It lacks details on ordering, error states, or rate limits, but is adequate for a read-only tool.

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

Conciseness3/5

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

The description is front-loaded with the main purpose, but includes a lengthy '数据展示建议' section that is more about agent behavior than tool definition. This could be trimmed or moved to a separate note to improve conciseness.

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?

Given the tool has an output schema, the description need not detail return values. It covers purpose, parameters (including defaults and behavior), and provides agent guidance on data presentation. It does not mention pagination or ordering, but overall is complete enough for agent use.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate. It explains the platforms parameter in detail: example IDs, default behavior (use config), supported platforms from config. It explains limit default, max, and actual count may vary. It explains include_url default false and token savings. This adds significant meaning beyond property names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence clearly states the tool gets the latest batch of crawled news data to quickly understand current hotspots, specifying the verb (get) and resource (latest news). It is distinct from sibling tools like search_news.

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

Usage Guidelines4/5

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

The description provides extensive context on when and how to present data to users, including when to summarize (e.g., when user explicitly asks) and when to show full data. However, it does not explicitly contrast with sibling tools like search_news for specific scenarios.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/YangLang116/TrendRadar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server