Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bleacherreport_headlines

Fetch newest headlines for a Bleacher Report league or sub-hub by section slug, returning article titles, URLs, and publication times.

Instructions

Get Bleacher Report section headlines. Returns the stories on one Bleacher Report league or sub-hub page, newest first. section is required and takes a slug such as nfl, nba-draft, formula-1 or recruiting. Each has a headline, article URL and publication time, plus thumbnail and blurb when present. Busy leagues return 100 or more stories, quiet ones only a few.

Input Schema

NameRequiredDescriptionDefault
sectionYesBleacher Report section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/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 ordering ('newest first'), the shape of each item (headline, article URL, publication time, optional thumbnail and blurb), and volume variability ('100 or more' for busy leagues vs 'only a few'). It omits auth/rate-limit considerations, but adds meaningful behavioral context.

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?

Four sentences, front-loaded with purpose and scope, then parameter guidance, then return shape, then volume expectations. Each sentence contributes; nothing is redundant or padded.

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, and the description compensates by describing the returned fields and ordering, and by setting expectations on result count. Complete for a one-param list tool, with only minor gaps around whether results are truncated or paginated.

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 every valid slug, so the schema does the heavy lifting. The description still adds value by illustrating the slug format with examples (nfl, nba-draft, formula-1, recruiting), matching the baseline 3 for a well-documented single param.

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 Bleacher Report section headlines') and clarifies the scope is one league or sub-hub page, newest first. It distinguishes itself from the sibling bleacherreport_news/sections tools implicitly through the per-section framing, but never names an alternative explicitly.

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 the scoping language ('one Bleacher Report league or sub-hub page') and the required `section` slug, but there is no explicit guidance on when to pick this over bleacherreport_news, bleacherreport_sections, or bleacherreport_article.

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