Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ninetofivemac_headlines

Fetch the newest 9to5Mac headlines for a specific topic guide by section slug, returning up to 100 posts with title, URL, summary, time, and author.

Instructions

Get 9to5Mac section headlines. Returns the newest posts from one 9to5Mac topic guide, up to 100. section is required and takes a guide slug such as iphone, macbook-pro, vision-pro or how-to; an unknown or missing value returns an invalid-params error. Smaller guides, such as apple-watch-se, return fewer. Items carry title, URL, summary, time and author.

Input Schema

NameRequiredDescriptionDefault
sectionYes9to5Mac guide slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/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 does well: it discloses the 100-item cap, the invalid-params failure mode for bad slugs, and that smaller guides return fewer results. It omits auth/rate-limit behavior and any pagination story, which keeps it from a 5.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the core action, then the parameter contract, then the return shape. Every sentence carries information and none is redundant with the schema or annotations.

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?

There is no output schema, so the description usefully enumerates the returned item fields (title, URL, summary, time, author) along with the cap and error behavior. For a single-required-param feed tool, an agent has everything needed to call it correctly.

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?

Schema coverage is 100% and the enum already enumerates valid slugs, so the baseline is 3. The description adds real value on top: it explains that the value is a guide slug, gives representative examples, and defines the error behavior for unknown values plus the count effect for niche guides.

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 section headlines') and narrows the scope to 'one 9to5Mac topic guide', which implicitly separates it from the sibling news/article tools. It stops short of naming or contrasting any sibling explicitly, so an agent must infer the distinction from the phrase 'section headlines'.

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?

It gives concrete usage constraints: `section` is required, takes a guide slug, and an unknown or missing value yields an invalid-params error. However, it never says when to prefer this tool over siblings like ninetofivemac_news or ninetofivemac_sections, so the routing guidance is only implied.

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