Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ninetofivemac_article

Retrieve structured 9to5Mac article content by canonical URL, including title, description, authors, section, images, and body paragraphs, without affiliate disclaimers or embedded-tweet text.

Instructions

Get 9to5Mac article content. Returns a 9to5Mac article by url, a canonical 9to5mac.com address in the form /YYYY/MM/DD/<slug>/: title, description, publication and update times, authors, section, image and the body paragraphs. The affiliate FTC disclaimer and embedded-tweet text are left out, and paywalled is never set because the articles are free.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical 9to5Mac article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/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 delivers well: it enumerates what is returned (title, description, times, authors, section, image, paragraphs), discloses deliberate exclusions (FTC disclaimer, embedded-tweet text), and clarifies that `paywalled` is never set. Missing only auth/rate-limit detail, which is minor for a free public source.

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?

Front-loads the purpose in the first sentence, then packs returns and exclusions densely with no filler. Slightly information-thick, but every clause earns its place.

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?

No output schema exists, so the description must describe returns, and it does so thoroughly, including edge-case behavior. Combined with a fully documented single parameter, an agent has enough to invoke and interpret 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 schema label is generic, but the description adds real meaning by specifying the canonical URL shape `/YYYY/MM/DD/<slug>/`, disambiguating acceptable inputs beyond the schema's bare 'Canonical 9to5Mac article URL'.

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 and resource: 'Get 9to5Mac article content', and immediately names the identifying input. Among dozens of *_article siblings, the 9to5Mac-specific scope is unambiguous.

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 explains the required input form ('by `url`, a canonical `9to5mac.com` address'), which implies when it applies, but gives no explicit when-to-use vs alternatives or preconditions. Usage is inferable from the name, not stated.

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