Crawlora MCP

yahoo_sports_video_headlines

Read-only

Fetch current Yahoo Sports headline cards for one list_id from yahoo_sports_video_list_catalog. count accepts 1 or 6 as used by the page and defaults to 6; an empty live-channel list is valid. Playback streams are not returned.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "list_id": "<list_id>"
    },
    "name": "yahoo_sports_video_headlines"
  }
}

Input Schema

Name	Required	Description	Default
`count`	No	Optional. Yahoo page request count: 1 or 6. Defaults to 6.
`list_id`	Yes	Required. Yahoo video list ID from the Watch page's videoListId or VideoListId field.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare read-only and open-world, so the bar is lower; the description still adds real behavioral context: count is constrained to 1 or 6 with a default of 6, and an empty live-channel list is a valid response (preventing an agent from retrying or treating it as an error). It does not discuss caching or freshness beyond 'current'.

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 short sentences, each carrying distinct information: identity+provenance, count constraint, and response caveats. Nothing is redundant and the identifying clause is front-loaded.

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 read tool with full schema coverage, complete annotations, and an output schema that documents the return shape, the description covers the remaining agent-relevant gotchas: where list_id comes from, the legal count values, empty-list validity, and the absence of playback streams.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both list_id provenance and the '1 or 6, defaults to 6' count constraint. The description largely restates those facts rather than adding new meaning such as what the difference between count=1 and count=6 produces; baseline 3 is appropriate.

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 concrete verb ('Fetch') and resource ('current Yahoo Sports headline cards') scoped to a single list_id, and explicitly names the sibling tool yahoo_sports_video_list_catalog as the source of that ID. An agent can distinguish this from the catalog and other Yahoo Sports video tools without opening a 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?

It establishes the prerequisite (list_id must come from yahoo_sports_video_list_catalog) and a scope exclusion ('Playback streams are not returned'), which steers an agent away from using this for stream URLs. It stops short of naming a concrete alternative for playback data, so it is strong context rather than a full use/avoid matrix.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.