Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ninetofivemac_news

Fetch top Apple news stories and podcast posts from 9to5Mac with no input, returning titles, URLs, summaries, authors, images, and publication times.

Instructions

Get 9to5Mac top stories. Returns the latest 9to5Mac Apple news stories with no input needed. Each item has a title, canonical article URL, summary, publication time, author and image when present. The list can include podcast episode posts, such as Happy Hour and 9to5Mac Daily, alongside news articles.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/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 disclose meaningful behavior: the return fields (title, URL, summary, publication time, author, image when present) and the caveat that podcast episode posts can appear alongside articles. It omits any note on result count, pagination, or freshness window, but the core behavioral picture is clear.

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?

Four short sentences, front-loaded with the purpose before the return details. Slight redundancy between 'Get 9to5Mac top stories' and 'Returns the latest 9to5Mac Apple news stories,' but nothing that wastes significant space.

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?

There is no output schema, so the description must describe the payload, and it enumerates the fields plus the podcast-post caveat. For a zero-parameter feed tool this is nearly complete; only volume/ordering details are absent.

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 explain and the schema-coverage baseline of 4 applies. No param-related content is needed or missing.

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 9to5Mac top stories') and clarifies it returns the latest Apple news stories. It does not, however, explicitly differentiate itself from close siblings like ninetofivemac_headlines or ninetofivemac_article, so an agent must infer the distinction from the wireframe of names.

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?

The phrase 'with no input needed' tells the agent this is a zero-argument fetch, which is useful context. But there is no explicit when-to-use guidance and no named alternative (e.g., headlines, sections, article) to route between, leaving selection to inference.

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