Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_sports_video_headlines

Retrieve Yahoo Sports video headline cards by list_id from a Watch or video-show page, with count set to 1 or 6 for page-aligned results.

Instructions

Yahoo Sports video headlines. Returns video cards from Yahoo's public storyheadlines list. Use a list_id from yahoo-sports-video-list-catalog or a Yahoo video-show page; count supports the page's observed values 1 and 6.

Input Schema

NameRequiredDescriptionDefault
countNoYahoo page request count: 1 or 6. Defaults to 6.
list_idYesYahoo video list UUID from a Watch or video-show page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral burden. It signals a read-only public data source ('Yahoo's public storyheadlines list') and usefully explains the odd count restriction ('page's observed values 1 and 6'), but it doesn't describe the return shape, ordering, pagination, or any rate/identity constraints.

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?

Front-loads the core purpose, then the sourcing hint, then the count constraint — three tight sentences with no filler. Slightly dense but every clause earns its place.

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 two-parameter read tool with no output schema, the description covers the essential calling details: what it returns, where list_id comes from, and the constrained count values. Return structure is only roughly indicated ('video cards'), which is a minor gap given no output schema exists.

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 clear enum, so the baseline is 3. The description goes beyond the schema by explaining why count is limited to 1 and 6 (observed page values) and by giving concrete sources for list_id, adding real semantic value.

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: returns video cards from Yahoo's public storyheadlines list. It distinguishes this from the sibling yahoo_sports_video_list_catalog by positioning that tool as the source of list_id, making the division of labor clear without needing to open either schema.

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?

Explicitly directs how to source the required list_id (from yahoo-sports-video-list-catalog or a Yahoo video-show page), which is the key prerequisite an agent needs. It lacks an explicit 'when not to use' or a description of the filtering scope, but the sourcing guidance is clear and actionable.

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