Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cbssports_headlines

Fetch CBS Sports headlines by section slug, such as nfl, soccer, or betting. Get each item's title, URL, summary, author, time, and image.

Instructions

Get CBS Sports section headlines. Returns fresh headlines from one CBS Sports per-sport feed. section is required and takes one of 21 slugs, such as nfl, college-basketball, soccer, ufc, betting or general. Each item has a title and URL, and may carry a summary, author, publication time and image.

Input Schema

NameRequiredDescriptionDefault
sectionYesCBS Sports section slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/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 burden. It usefully discloses that results are 'fresh' and scoped to one per-sport feed, and previews the item shape (title, URL, optional summary/author/time/image). However, it omits auth requirements, rate limits, and any pagination or result-count behavior for an unannotated read tool.

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 tight sentences: purpose, parameter constraint with examples, then return shape. Front-loaded and every sentence contributes information with no padding.

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 summarizing the returned item fields. For a single-parameter read tool this is nearly complete, with only minor gaps around volume/pagination.

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% and the enum is fully enumerated, so the schema already documents the parameter. The description adds value by stating `section` is required, confirming the count (21 slugs), and giving concrete examples (nfl, college-basketball, soccer, ufc, betting, general) that aid selection.

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 CBS Sports section headlines') and clarifies scope as 'fresh headlines from one CBS Sports per-sport feed'. This clearly separates it from generic news tools, though it does not explicitly name the sibling it differs from (e.g., cbssports_news).

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 required `section` parameter implies the tool is for fetching a single sport's feed, but there is no explicit when-to-use guidance or routing to alternatives like cbssports_news or cbssports_sections. Usage must be inferred.

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