Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

time_author

Fetch a TIME author's profile and recent articles from a canonical author URL, returning name, title, bio, image, social links, and article details.

Instructions

Get a TIME author profile. Returns a TIME author's profile by url, a canonical time.com/author/<slug>/ link: name, job title, bio, image URL, social account links and recent articles with title, URL, excerpt, section, section URL and ISO-8601 published_at. Not every author lists a social account.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical TIME author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the returned payload (name, job title, bio, image, social links, recent articles with nested fields) plus a genuine caveat that social accounts may be absent. However, it says nothing about error behavior for a non-canonical URL, how many 'recent articles' are returned, or any auth/rate-limit constraints, so it is helpful but incomplete.

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, purpose front-loaded, then return details. The field list is dense but each item is informative; minor verbosity in re-listing nested article fields, but no filler.

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?

No output schema exists, so the description must describe the return payload, and it does so thoroughly, along with the required URL format. The only gap is the absence of count/limit and error semantics on an otherwise simple one-parameter fetch.

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 already 100% ('Canonical TIME author URL'), so baseline is 3; the description adds real value by specifying the exact canonical form, `time.com/author/<slug>/`, which tells the agent how to construct or validate the value.

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 TIME author profile') and names the site explicitly, which matters given the large field of look-alike *_author siblings (usmagazine_author, vox_author, cbsnews_author, etc.). The return-field enumeration further pins down exactly what this tool produces.

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: the agent infers it should call this to fetch an author profile, and the description supplies the expected input shape (canonical time.com/author/<slug>/ URL), which functions as a how-to. But there is no when-to-use/when-not guidance and no pointer to alternatives such as time_article or time_news for other TIME 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