Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

macrumors_article

Fetch structured MacRumors article content from a canonical URL, including title, authors, publish time, images, and body paragraphs for news posts, guides, how-tos, and reviews.

Instructions

Get MacRumors article content. Returns a MacRumors article by url: a dated news post, or a /guide/, /how-to/ or /review/ page. The response has the title, description, section, authors, lead image, publish time, updated_at and body paragraphs. Roundup, author and forum URLs are rejected. Reviews have no updated_at, and paywalled is omitted.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical MacRumors article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.4/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 behavioral burden and does so well: it lists the returned fields, warns that roundup/author/forum URLs are rejected, and notes that reviews lack `updated_at` and omit `paywalled`. No auth requirements or rate limits are mentioned, so it stops short of 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 purpose before scope, response shape and edge cases. Every sentence adds information with no filler.

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 and no annotations, so the description must explain the return shape and caveats; it does both (field list, missing `updated_at` on reviews, omitted `paywalled`). It is nearly complete, missing only any notion of error handling or the exact type of the body content beyond `paragraphs`.

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 baseline is 3, but the description adds real meaning beyond the schema's 'Canonical MacRumors article URL' by enumerating which URL patterns are valid (/guide/, /how-to/, /review/, dated posts) and which are rejected.

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+resource ('Get MacRumors article content'), then sharpens it to fetching a single article by URL. This is clearly distinguished from siblings like macrumors_headlines, macrumors_news, macrumors_author and macrumors_sections, which return collections rather than one article body.

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?

Gives clear context for accepted inputs (a dated news post, or a /guide/, /how-to/ or /review/ page) and explicitly rejects roundup, author and forum URLs. That is strong when-not-to-use guidance, though it never names an alternative sibling tool to use instead for those rejected cases.

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