Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_sports_section_stream

Fetch a paginated page of Yahoo Sports section articles by section URL and page offset, returning raw article references with nested content, tags, and provider metadata.

Instructions

Yahoo Sports public section article stream. Returns one page from the public article stream embedded by a Yahoo Sports section page. The service reads the page's current list ID and source parameters from Flight data, then mirrors Yahoo's POST /api/content/ request. Items remain raw AssetRef objects, preserving nested content, tags, provider metadata, and new upstream fields. Use a section_url discovered from yahoo-sports-navigation; current examples include /indycar/ and /motogp/. Pages without an article stream are rejected. The only exposed page selector is Yahoo's integer pageOffset; it defaults to the page's embedded initial offset. Use page_info.start + page_info.count to request the next page. No server-side tag, sort, or category filter is added because the page does not expose one on this stream.

Input Schema

NameRequiredDescriptionDefault
page_offsetNoExact upstream pageOffset. Defaults to the section page's initial offset; use page_info.start + page_info.count for the next page
section_urlYesFull HTTPS Yahoo Sports article-list URL from yahoo-sports-navigation

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden and does so well: it discloses raw AssetRef return objects, preservation of nested content and metadata, upstream POST mirroring, rejection of non-stream pages, and pagination behavior via page_info.start + page_info.count.

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?

The definition is front-loaded with purpose and pagination guidance, and every sentence is relevant. Some upstream implementation detail about Flight data and mirroring POST /api/content is slightly verbose, but it supports transparency rather than padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter paginated stream tool with no output schema, the description is complete: it explains the input source, pagination math, return shape, and rejection conditions. Nothing critical is missing.

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 already 100%, so this dimension has a baseline of 3. The description adds useful meaning by explaining that page_offset is the only exposed selector, defaults to the page's embedded initial offset, and that the next page is computed from page_info.start + page_info.count.

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: it returns one page from the Yahoo Sports public section article stream embedded by a section page. It distinguishes itself from general news siblings by tying the input to a section page and a raw upstream article stream.

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 clear usage guidance: use a section_url discovered from yahoo-sports-navigation, and pages without an article stream are rejected. It also explains the only pagination selector and that no server-side filtering exists, though it does not explicitly compare itself to sibling news tools.

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