Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ninetofivemac_author

Retrieve a 9to5Mac author profile from a canonical author URL, returning name, avatar, biography, social links, and recent articles.

Instructions

Get a 9to5Mac author profile. Returns a 9to5Mac author profile from url, a canonical https://9to5mac.com/author/<slug>/ address: name, avatar, biography, social_links and the first page of recent articles. Each social link's type comes from the page's icon, and each article's published_at is the page's own text, such as 9 hours ago, not a timestamp.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical 9to5Mac author URL

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 behavioral burden and does so well: it lists the returned fields, clarifies that only the first page of articles is returned, and discloses that social link 'type' comes from the page icon and 'published_at' is relative text rather than a timestamp. It does not cover auth or rate limits, but the key data quirks are surfaced.

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 purpose and then precise return-value details. Every sentence adds useful 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?

No output schema exists, so the description must explain return values; it does by listing fields and two data quirks. It could specify how many articles 'first page' means, but it is otherwise complete enough for an agent to call the tool 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 description coverage is 100%, so the schema already documents the single parameter. The description adds value by specifying the exact canonical URL pattern (`https://9to5mac.com/author/<slug>/`), which is more concrete than the schema's 'Canonical 9to5Mac author 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?

The description starts with a specific verb+resource ('Get a 9to5Mac author profile') and immediately names the source site and the required URL format, so an agent can distinguish it from article/headline siblings. The listing of returned fields further reinforces the exact purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains what the tool returns but gives no guidance on when to choose it over alternatives (e.g., ninetofivemac_article, ninetofivemac_headlines, or other author tools). It implies usage only by stating the URL must be a canonical author address.

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