Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

screenrant_headlines

Fetch recent ScreenRant headlines for one section slug, returning about 10 items as structured JSON for content monitoring and research.

Instructions

Get ScreenRant section headlines. Returns about 10 of the most recent ScreenRant items for one section. section is required and takes one of 34 slugs such as movie-news, tv-reviews, reality-tv, comics, game-news or anime. Items in videos, and some in interviews and movie-trailers, link to /video/<slug>/ pages that screenrant-article rejects.

Input Schema

NameRequiredDescriptionDefault
sectionYesScreenRant RSS section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.5/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 behavioral burden. It usefully discloses the approximate result count and the cross-tool caveat about video URLs that the article tool rejects. It says nothing about authentication, rate limits, pagination, or whether the section list is exhaustive.

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?

Three front-loaded sentences: purpose and payload first, parameter requirement second, cross-tool caveat last. Little waste, though the caveat sentence is slightly dense and could be tighter.

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?

With no output schema, the description correctly compensates by describing the return payload size and nature. Combined with a fully documented enum parameter, an agent has what it needs to call the tool, though the boundary with sibling headline tools remains unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the enum already enumerates all 34 slugs, so the schema does the heavy lifting. The description adds only light confirmation ("required", "34 slugs", a handful of examples), which is baseline-level value rather than new semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Get ScreenRant section headlines") and quantifies the payload ("about 10 of the most recent ScreenRant items for one section"). It also distinguishes itself from `screenrant-article` by noting that video-linked items are rejected there. It does not, however, distinguish itself from close siblings like `screenrant_news` or `screenrant_sections`.

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 note that `/video/<slug>/` items are rejected by `screenrant-article` hints that this tool is the route for those, but there is no explicit "use this when... use X instead when..." guidance against the other screenrant siblings. An agent must infer the selection rule.

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