Skip to main content
Glama

get_latest_news

Fetch newly scraped news from selected platforms to see what is trending now. Adjust result count, platforms, and URL inclusion as needed.

Instructions

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

Args: platforms: 平台ID列表,如 ['zhihu', 'weibo'],不指定则使用所有平台 limit: 返回条数限制,默认50,最大1000 include_url: 是否包含URL链接,默认False(节省token)

Returns: JSON格式的新闻列表

数据展示建议

  • 默认展示全部返回数据,除非用户明确要求总结

  • 用户说"总结"或"挑重点"时才进行筛选

  • 用户问"为什么只显示部分"说明需要完整数据

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
platformsNo
include_urlNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the full disclosure burden. It explains parameter tradeoffs (include_url default False to save tokens) and provides explicit display behavior advice ('默认展示全部返回数据...用户说总结...'), giving agents non-obvious interaction guidance. It lacks error handling or rate limit info, but that's less critical for a read-only fetch.

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

Conciseness4/5

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

The description opens with a one-sentence summary, then logically organizes Args, Returns, and display suggestions. The additional '数据展示建议' section is extra but earns its place by guiding agent behavior. Slightly verbose but well-structured.

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

Completeness5/5

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

Given the tool's simplicity (3 optional parameters, output schema present), the description covers parameter semantics, return format, and even display behavior. It is complete enough for an agent to invoke correctly and handle results appropriately.

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?

The schema has zero descriptions for its 3 parameters, but the description fully compensates by explaining each parameter in detail: 'platforms: 平台ID列表', 'limit: 返回条数限制,默认50,最大1000', 'include_url: 是否包含URL链接,默认False(节省token)'. This adds meaning far beyond the raw schema.

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 description uses a specific verb and resource: '获取最新一批爬取的新闻数据' meaning 'get the latest batch of crawled news data.' It clearly distinguishes from siblings like search_news or get_news_by_date by focusing on the latest crawled batch.

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 implies this tool is for quickly checking current hot topics ('快速了解当前热点'), which provides clear context. However, it does not explicitly mention alternatives or exclusions, so agents must infer when to use other tools.

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/2134863176/TrendRadar'

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