Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

macrumors_author

Retrieve a MacRumors author profile and recent articles by slug or canonical URL. Provide one identifier to get name, bio, image, and about 20 recent posts.

Instructions

Get a MacRumors author profile. Returns a MacRumors author profile, identified by slug (such as juli-clover) or a canonical macrumors.com/author/<slug> url; provide exactly one. The response has the name, bio, image_url and about 20 recent articles with title, URL, publication time and, when shown, summary and image. Unknown authors return not found.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical macrumors.com/author/<slug> URL; alternative to slug
slugNoAuthor slug, e.g. juli-clover

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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 well: it discloses the payload (name, bio, image_url, ~20 recent articles with fields) and the failure mode ('Unknown authors return not found'). It omits auth/permission or rate-limit context, but for a public read of a profile that is a minor gap.

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?

One tight paragraph, front-loaded with purpose, then identification, then payload, then error behavior. Every clause carries information; nothing is redundant.

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 the return shape, and it does so in detail (author fields plus article list contents). Combined with the input contract and not-found behavior, an agent has everything needed to call and interpret it.

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 baseline is 3, but the description adds genuine meaning beyond the schema: the example slug 'juli-clover', the exact URL shape, and the mutual-exclusivity rule 'provide exactly one'. That constraint is semantic value the schema alone only implies.

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 a MacRumors author profile') and immediately names the site, distinguishing it from the many other *_author siblings for other publications. An agent can tell exactly what this retrieves without opening the schema.

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?

Clearly frames the identification contract ('identified by slug ... or a canonical url; provide exactly one'), which tells the agent how to invoke it. It does not, however, contrast with siblings like macrumors_article or macrumors_headlines or state when an author profile is the wrong tool, so it stops short of full routing guidance.

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