Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

sportingnews_headlines

Fetch up to 20 Sporting News US headlines for a selected sport, league, or topic using a required section slug; returns titles, URLs, summaries, publication times, authors, and images.

Instructions

Get Sporting News section headlines. Returns up to 20 of the newest Sporting News US stories for one sport, league or topic. section is required and takes one of 44 slugs such as nfl, nba, mlb, premier-league, formula-1, ufc or college. Each item has its title, URL, summary, publication time, author and image. Off-season leagues may return older stories.

Input Schema

NameRequiredDescriptionDefault
sectionYesSporting News section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/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 stating that it returns up to 20 newest US stories, listing returned fields, and warning that off-season leagues may return older stories. It does not cover error behavior for invalid slugs, auth needs, or pagination.

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?

The description is front-loaded with the core purpose and then adds return size, parameter requirements, item fields, and an edge-case caveat without wasted text. Each sentence contributes useful context for this simple one-parameter tool.

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 read tool with no output schema or annotations, the description is largely complete: it explains the required slug, return count, item fields, and a freshness caveat. A small gap remains around invalid-section behavior or pagination, but neither is critical here.

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 coverage is 100%, and the enum already lists all 44 slugs, so the schema does the heavy lifting. The description adds examples and clarifies that `section` is one sport, league, or topic, but much of this repeats schema information rather than adding 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?

The description gives a specific verb and resource: "Get Sporting News section headlines," and scopes it to one sport, league, or topic with up to 20 newest stories. It is clear but does not explicitly distinguish itself from sibling tools such as sportingnews_news or sportingnews_article.

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 usage context is implied by "for one sport, league or topic" and the required `section` slug, but there is no explicit when-to-use guidance against alternatives like sportingnews_news or sportingnews_article. It also lacks exclusions or prerequisites beyond the required parameter.

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