Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

screenrant_author

Fetch a ScreenRant writer profile from a canonical URL to get name, title, bio, image, social links, and about 20 recent articles. Older pages are unavailable.

Instructions

Get a ScreenRant author profile. Returns a ScreenRant author's profile by canonical url (https://screenrant.com/author/<slug>/): name, title, biography, image, social links (such as x, linkedin, youtube or muckrack) and about 20 articles from the profile's Latest module. Older pages are not available.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical ScreenRant author URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

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 behavioral burden, and it does well: it enumerates the returned fields (name, title, biography, image, social links, ~20 articles) and discloses a real limitation about older pages. It omits auth/rate-limit context, but for a read-only profile fetch this is solid disclosure.

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, front-loaded with the purpose, then the return payload and the pagination limit. No filler; every clause adds information an agent needs.

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 tool with no output schema, the description usefully fills the return-value gap by listing the fields returned and the ~20-article cap. It is close to complete; only authentication/error behavior is unaddressed.

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% with a single parameter, so the baseline is 3, but the description adds value by giving the concrete URL template (https://screenrant.com/author/<slug>/) rather than leaving the format implicit. This exceeds what the schema's "Canonical ScreenRant author URL" alone conveys.

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+resource ("Get a ScreenRant author profile") and immediately scopes it to a canonical author URL, which cleanly separates it from sibling tools like screenrant_article, screenrant_news, and screenrant_sections. 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?

The description implies usage (fetch a profile given a URL) and flags one constraint ("Older pages are not available"), but it never states when to choose this over a search/listing sibling or what prerequisites exist. Usage is inferable rather than spelled out.

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