Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

yahoo_sports_golf_player_news

Retrieve a golfer's Yahoo Sports news stories and videos from their News tab, with Top or Latest modes and cursor-based pagination for follow-up pages.

Instructions

Yahoo Sports golf player news. Returns the story and video edges in one golfer's News tab. Latest mode returns Yahoo's opaque cursor and supports the same upstream cursor POST for subsequent pages.

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": {
      "player_url": "<player_url>"
    },
    "name": "yahoo_sports_golf_player_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoTop News or Latest
cursorNoOpaque next_cursor returned by a previous latest response
player_urlYesCanonical Yahoo Golf player URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.9/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that the tool returns story and video edges and that latest mode provides a cursor for paginated requests, though it does not cover auth needs, rate limits, or error behavior.

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?

The description is three short sentences, front-loads the tool's purpose, and then adds only relevant detail about output and pagination. There is no wasted text.

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 simple read-only retrieval tool with one required URL parameter and full schema coverage, the description provides enough context about what is returned and how latest-mode pagination works. It could optionally mention where to obtain the canonical player_url, but the core invocation requirements are covered.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful context about the cursor being opaque and used for subsequent pages, and it clarifies the latest-mode pagination flow beyond the raw enum and field descriptions.

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 clearly states the resource and output: one golfer's News tab, returning story and video edges. It is specific enough to separate this from the general golf player tool, though it does not explicitly contrast with sibling tools like yahoo_sports_golf_player or yahoo_sports_news.

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?

The description explains that latest mode returns an opaque cursor and supports subsequent cursor-based pages, which implies when to use latest for pagination. It does not explicitly say when to use top versus latest, nor does it point to alternatives for other golf-related needs.

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