Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

screenrant_article

Fetch ScreenRant article content from a canonical URL, returning title, authors, publication times, image, and body paragraphs as structured JSON for content analysis.

Instructions

Get ScreenRant article content. Returns a ScreenRant article by canonical url of the form https://screenrant.com/<slug>/: title, description, section, authors, publication and update times, image and body paragraphs. Warning and note callouts and Related cards are left out of paragraphs. Section hubs and multi-segment URLs such as /video/<slug>/ are rejected as invalid.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical ScreenRant article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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, states that warning/note callouts and Related cards are omitted from `paragraphs`, and documents failure behavior for non-canonical URLs. It omits auth, rate-limit, and truncation/caching behaviors, keeping it short of a 5.

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 the action and validation constraint, followed by return contents and omissions. Every sentence adds distinct information with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description's enumeration of returned fields and its note about excluded content (callouts, Related cards) is exactly what an agent needs. Combined with the URL validation rules, nothing essential for correct invocation 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?

The single `url` parameter is already documented at 100% schema coverage (baseline 3), and the description adds real value beyond the schema by specifying the required canonical form and the accepted/rejected URL patterns. It does not describe slug normalization or whether trailing paths/query strings are tolerated.

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 states a specific verb and resource ('Get ScreenRant article content') and enumerates the returned fields (title, description, section, authors, times, image, paragraphs), which clearly separates it from sibling listing tools such as screenrant_headlines and screenrant_news. An agent can identify the resource 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear positive conditions (canonical `https://screenrant.com/<slug>/` URLs only) and explicit exclusions: section hubs and multi-segment URLs like `/video/<slug>/` are rejected. It stops short of naming a sibling tool to use instead when a URL is a hub or video, so it is strong context but not full when/when-not routing.

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