Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cbssports_article

Extract structured CBS Sports article content from a canonical article URL, including title, authors, dates, lead image, and body paragraphs. Rejects video, scores, schedule, and player pages.

Instructions

Get CBS Sports article content. Returns a CBS Sports article by url, a canonical https://www.cbssports.com/<sport>/news/<slug>/ address, including nfl/draft/news/ and fantasy football news: title, description, publication and update times, authors, lead image and body paragraphs. Video, scores, schedule and player pages are rejected. paywalled is omitted because the articles are free.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical CBS Sports article URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 disclose real behavior: the accepted URL shape, that non-article page types are rejected, and that content is free (`paywalled` omitted). It does not mention error handling, rate limits, or whether fetching is idempotent, leaving some gaps for a no-annotation tool.

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?

Purpose is front-loaded and the sentence that follows is dense with useful detail (return fields, URL format, rejected page types, free access). Slightly packed but every clause contributes; no filler.

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 single-parameter fetch with no output schema, the description adequately explains the return content and access model, which compensates for the absent output schema. Minor gaps around failure modes remain, but an agent has enough to call it correctly.

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% with a single required `url`, so baseline is 3. The description adds value beyond the schema's terse 'Canonical CBS Sports article URL' by spelling out the canonical format and edge cases like `nfl/draft/news/`, clarifying exactly which URLs are valid.

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

Purpose5/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 article content') and enumerates exactly what is returned (title, description, pub/update times, authors, lead image, body paragraphs). This clearly separates it from the cbssports_author/headlines/news/sections siblings, which do not return article bodies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives concrete when-to-use guidance (canonical `https://www.cbssports.com/<sport>/news/<slug>/` URLs, including `nfl/draft/news/` and fantasy football) and explicit exclusions (video, scores, schedule and player pages are rejected). It stops short of naming the sibling to use for those rejected page types, so it is not a full when/when-not/alternatives.

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