Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

sciencealert_author

Retrieve a ScienceAlert author profile and one page of articles from an author listing URL to get bio, social links, and pagination details.

Instructions

Get a ScienceAlert author profile. Returns a ScienceAlert author's profile and one page of articles, from an author listing url in the form https://www.sciencealert.com/<author>/page/<number>; the first observed page is /page/0. The response has the name, slug, biography, image, social links, that page's articles, and page and has_next_page for paging.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesCanonical ScienceAlert author listing URL, e.g. /michelle-starr/page/0

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.7

TDQS

A4.1/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 a good job: it discloses pagination semantics (one page per call, page and has_next_page returned, first observed page is /page/0) and the exact URL shape required. It omits any auth/rate-limit or error context, but for a read-only listing tool the behavioral disclosure is solid.

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?

Front-loaded with the one-line purpose, then details on the URL form and return contents. Each sentence carries information, though the middle clause packing the URL template and page-number convention together is slightly dense.

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 explain returns, and it enumerates the profile fields, that page's articles, and the paging fields. Combined with a single fully-documented parameter, this is nearly complete; only explicit when-to-use guidance is missing.

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 meaning beyond the schema: it gives the full templated URL form with <author>/page/<number> and explains that /page/0 is the first observed page, which the schema example alone does not spell out.

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 ScienceAlert author profile') and immediately clarifies that it returns a profile plus one page of articles. This distinguishes it from siblings like sciencealert_article, sciencealert_headlines, and sciencealert_news, which an agent can route away from without opening any 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: use this when you want an author's profile and their paginated article listing. However, it never explicitly states when to choose this over sciencealert_article or sciencealert_news, nor any prerequisites such as needing a valid author slug. Adequate but leaves routing to inference.

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