Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cbssports_news

Fetch current CBS Sports headlines across all sports, returning article links with titles, summaries, authors, and publish dates while filtering out video, scores, schedules, and player pages.

Instructions

Get CBS Sports top stories. Returns the current CBS Sports headlines across every sport, with no input needed: news stories, analysis columns and picks or predictions articles. Only article links are returned; video, scores, schedule and player pages are filtered out. Items have title and url, plus summary, published_at and author when provided.

Input Schema

NameRequiredDescriptionDefault

No arguments

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 well: it discloses that no input is required, that only article links are returned, that video/scores/schedule/player pages are filtered out, and the exact item fields (title, url, summary, published_at, author). It omits any mention of result count, pagination, or fetch/auth behavior, which keeps 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the purpose, then scope, then return shape. No filler, though the em-dash list of article types is slightly dense. Efficient overall.

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, no annotations, and no parameters, the description provides enough: it names the returned fields and the filtered-out content types, so an agent knows what to expect. Missing details like item count or pagination behavior are minor for a no-arg feed tool.

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 tool takes zero parameters, so the baseline is 4. The description reinforces this with 'no input needed', correctly setting the expectation that no arguments are required.

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+resource ('Get CBS Sports top stories') and enumerates the content types it covers (news stories, analysis columns, picks/predictions articles). It is clear on its own, but does not explicitly differentiate itself from the near-identical sibling cbssports_headlines, since it also calls its output 'headlines'.

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?

'with no input needed' and the list of excluded content (video, scores, schedule, player pages) imply when this tool is appropriate, but no alternative sibling is named and there is no explicit when-not guidance. Usage is inferable rather than stated.

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