Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

macrumors_headlines

Fetch up to 20 MacRumors headlines for a chosen section (front-page, guides, how-to, or reviews) with title, URL, author, publication time, summary, and image when available.

Instructions

Get MacRumors section headlines. Returns the newest 20 MacRumors entries for one section. section is required and takes front-page, guides, how-to or reviews; other values return an invalid-params error. Each item has its title, URL, author, publication time and short summary. Items from guides, how-to and reviews also carry a thumbnail image_url.

Input Schema

NameRequiredDescriptionDefault
sectionYesMacRumors section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 fixed return size (20), the invalid-params error for out-of-enum values, and that image_url only appears for guides/how-to/reviews. It does not mention auth or rate limits, but for a public read-only feed the safety profile is implicitly clear.

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 sentences, front-loaded with the core action, then scoping, then return shape. Every sentence carries information an agent needs, with no filler.

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?

No output schema exists, so the description must describe returns, and it does: title, URL, author, publication time, short summary, plus conditional image_url. Combined with the enum constraint and error behavior, 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%, so the enum values are already documented and the description's restatement of them is partly redundant. It nonetheless adds genuine semantics beyond the schema, notably that an unrecognized value produces an invalid-params error and that the parameter scopes the result to exactly one section.

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?

States a specific verb (Get) and resource (MacRumors section headlines) and pins the scope: the newest 20 entries for one section. An agent can distinguish it from siblings like macrumors_sections (which lists sections) or macrumors_news without opening any schema.

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 description conveys when the tool applies (fetching current headlines for a single section) and constrains the input, but it never names an alternative or states when-not to use it. For a headlines tool in a family of macrumors_* siblings, a routing hint would improve selection.

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