Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tomsguide_author

Fetch a Tom's Guide author profile by slug or URL, including name, title, bio, social links, and paginated recent articles.

Instructions

Get a Tom's Guide author profile. Returns a Tom's Guide author's name, job title, biography, social links and one page of recent articles. Give exactly one of slug or url; page is 1-based, defaults to 1 and overrides any page in url. The response also has page and has_next_page.

Input Schema

NameRequiredDescriptionDefault
urlNoCanonical tomsguide.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-pritchard

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?

No annotations are provided, so the description carries the full burden. It discloses the return payload (name, job title, biography, social links, one page of articles), the pagination mechanism (page defaults to 1, overrides url), and response metadata (page, has_next_page) – substantial behavioral detail for a read-only profile fetch.

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, each earning its place: purpose, return contents, and parameter rules – front-loaded with the core purpose and no waste.

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?

With no output schema, the description compensates by enumerating what comes back, and it covers the pagination model fully. An agent can call this correctly from the description alone.

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 real meaning beyond the schema: the mutual exclusivity of slug and url ('exactly one of') and the precedence rule that page overrides any page in url are not encoded in the schema.

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 ('Get') and resource ('Tom's Guide author profile'), and is immediately distinguishable from siblings like tomsguide_article, tomsguide_headlines, and tomsguide_sections.

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?

Gives an explicit construction rule: 'Give exactly one of `slug` or `url`.' It doesn't say when to prefer slug over url, nor route to any alternative sibling, but the key usage constraint is 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