Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ninetofivegoogle_author

Fetch a 9to5Google author profile from a canonical author URL. Returns name, bio, social links, and recent articles with titles, summaries, and images.

Instructions

Get a 9to5Google author profile. Returns a 9to5Google author profile from url, a canonical https://9to5google.com/author/<slug>/ address. The response has the author's name, avatar, biography, social_links and the first page of recent articles, each with title, URL, summary and image. Social-link types and dates are as the author's page shows them.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical 9to5Google author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.9

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return shape (name, avatar, biography, social_links, first page of recent articles) and adds a caveat that social-link types and dates reflect the author's page. It omits any auth/rate-limit notes, but for a public read-only fetch this is substantially transparent.

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, front-loaded with purpose then input format then return contents, with zero filler or repetition.

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 one-parameter fetch with no output schema, the description supplies the return-field breakdown an agent needs to decide if it's useful. It stops short of login/pagination details, but the core need is met.

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% and the single url param is already described, but the definition adds concrete value by giving the canonical format pattern 'https://9to5google.com/author/<slug>/', telling the agent exactly what shape of URL to supply.

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 ('Get a 9to5Google author profile') and clearly targets the author-profile entity, distinguishing it from sibling endpoints like ninetofivegoogle_article, _news, and _headlines. An agent can tell what it retrieves without opening the schema.

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 by naming the required canonical author URL, but the description never states when this tool should be chosen over siblings or what the input must look like beyond 'canonical'. There is no explicit when-not guidance.

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