Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

ninetofivegoogle_news

Fetch 9to5Google top stories without inputs, returning titles, canonical URLs, summaries, publication times, and authors while filtering out cross-network links.

Instructions

Get 9to5Google top stories. Returns recent 9to5Google stories with no input needed. Each item has a title, canonical URL, summary, publication time and author. Cross-network links are filtered out, so returned items use canonical 9to5Google story URLs.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

B3.4/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 add real value: it discloses the returned field set and the cross-network link filtering that guarantees canonical 9to5Google URLs. It stops short of other behavioral facts an agent would want for a feed tool — how many items are returned, how fresh they are, or whether results are paginated.

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?

Three tightly written sentences, front-loaded with the purpose and then the return shape and filtering rule. Each sentence adds information, though the closing clause about canonical URLs is slightly redundant with the earlier description of the return contents.

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-parameter feed tool with no output schema, the description does the essential work of describing the returned fields (title, URL, summary, publication time, author) and the URL-filtering behavior. The remaining gap is volume/freshness limits, which the description never sets.

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 clarify; the baseline for a 0-param tool is 4. The description correctly conveys that no input is required.

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 resource ('Get 9to5Google top stories') and enumerates the returned fields, so the agent knows exactly what it fetches. However, it never distinguishes itself from sibling ninetofivegoogle_headlines (or ninetofivegoogle_article/sections), which for other publishers serve a nearly identical 'top stories' role, leaving the agent to guess which of the two to call.

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

Usage Guidelines2/5

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

The only usage cue is 'with no input needed', which describes the call mechanics rather than when to choose this tool. No alternatives are named and no condition (e.g., 'use ninetofivegoogle_article to read a single story, headlines for a different feed') is given, even though several closely related 9to5Google siblings exist.

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

Deploy Server

Other Tools