Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

techradar_author

Fetch a TechRadar author's public profile, including name, biography, social links, and a page of recent articles by slug or URL.

Instructions

Get a TechRadar author profile. Returns one TechRadar author's public profile: name, biography, social links, and one page of their recent articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoCanonical techradar.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. tom-power

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses that the tool returns a public profile and only one page of recent articles, which is useful context. However, it does not disclose that at least one of url or slug is effectively required, nor error behavior or rate limits.

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?

Two sentences with no fluff: the first establishes the operation, the second lists return fields. It is well front-loaded, though it omits usage hints (e.g., the need to supply a slug or URL) without bloating the text.

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?

For a simple lookup tool, the description is fairly complete: it states purpose, return content, and a pagination limitation. It does not clarify that url and slug are alternative selectors, but the schema covers that semantics, and the absence of an output schema is partially mitigated by the listed return fields.

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?

All three parameters are fully described in the schema (100% coverage), so the description need not add parameter details. It loosely relates the 'page' parameter via 'one page of their recent articles' but adds no meaning beyond what the schema already states.

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?

The description states a specific verb ('Get') and resource ('TechRadar author profile') and lists what is returned (name, biography, social links, recent articles). It distinguishes from non-author TechRadar siblings like techradar_article and techradar_headlines, though it does not explicitly contrast with the many other *_author tools.

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 (to retrieve a TechRadar author profile) but there is no explicit when-to-use or when-not-to-use statement, and no alternatives are named. The agent must infer this is for author lookups rather than e.g. article content.

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