Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

tomsguide_author

Fetch a Tom's Guide author's public profile including biography, social links, and recent articles using their author slug or URL.

Instructions

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

Input Schema

TableJSON 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.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 burden of behavioral disclosure. It notes the profile is 'public' and that only 'one page' of articles is returned, adding some transparency. However, it does not discuss error behavior, rate limits, or parameter precedence, leaving gaps.

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?

Two sentences with no fluff; the action is front-loaded and the return fields are listed efficiently.

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?

The description covers the return payload and pagination limit, and the schema documents all parameters fully. It does not describe error cases or the relationship between url and slug, but those are in the schema. Sufficient for a simple retrieval tool.

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 description coverage is 100%, so the baseline is 3. The description's mention of 'one page' aligns with the page parameter but adds no new semantics beyond the schema's parameter descriptions.

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 opens with a specific verb-resource pair ('Get a Tom's Guide author profile') and enumerates the returned content (name, biography, social links, recent articles), making its purpose unmistakable and distinct from sibling tools like tomsguide_article or tomsguide_headlines.

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?

The description clearly states the tool's scope (one author profile) but does not explicitly mention when to prefer it over alternatives or provide exclusions. The intended use is implied by the purpose, so it earns a 4 rather than a 5.

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