Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tomshardware_author

Fetch a Tom's Hardware author profile by slug or URL to retrieve bio, job title, social links, and recent articles; use page to paginate results.

Instructions

Get a Tom's Hardware author profile. Returns a Tom's Hardware author profile with name, job title, biography, social links and one page of recent articles. Identify the author with slug (such as christian-eberle) or an author url; page (default 1) overrides any page in the URL. has_next_page tells you whether more articles exist.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical tomshardware.com/author/<slug> URL, optionally with a /page/<n> segment; alternative to slug
pageNo1-based page number; overrides any page number in url
slugNoAuthor slug, e.g. christian-eberle

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full burden and does well: it enumerates the returned fields, states that only one page of recent articles comes back, notes the default page value, explains that page overrides a page in the URL, and exposes has_next_page as the pagination signal. It stops short of error behavior for an unknown slug or whether any auth applies.

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?

Three tight sentences, front-loaded with the purpose and return contents, then identification and pagination mechanics. Minor redundancy in opening with both "Get a ... profile" and "Returns a ... profile" keeps it from a 5.

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?

With no output schema and no annotations, the description does the necessary work: it describes the returned fields, the pagination model, and how to address an author. A short note on invalid-slug behavior or article fields would complete it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and all three parameters are already documented, including the slug example and the page-overrides-url rule. The description restates those same facts rather than adding new syntax, format, or constraint information, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb + resource ("Get a Tom's Hardware author profile") plus a concrete inventory of what comes back (name, job title, biography, social links, one page of recent articles). The site-level prefixes of the many sibling *_author tools already distinguish them; the description does not explicitly route to tomshardware_article for article content, keeping it just below a 5.

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?

Usage is implied rather than stated: an agent infers "call this when you need an author's profile." It gives no when-not-to-use guidance and never names a sibling (e.g. tomshardware_article, tomshardware_news) as an alternative path.

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