Fetch Yahoo Sports news articles by league key, returning source headlines and article tags for sports monitoring, research, and league-specific news feeds.
Yahoo Sports league news. Returns source news articles. For league=soccer, Yahoo exposes a shared cross-competition /soccer/news/ feed and no competition-specific news filter; article tags are preserved verbatim.
| Name | Required | Description | Default |
|---|---|---|---|
| league | Yes | League key |
Changes observed during successful MCP inspections.
v1.17.18Input schema / properties / league / enumPrevious value: -[
- "nfl",
- "nba",
- "wnba",
- "mlb",
- "nhl",
- "college-football",
- "college-basketball",
- "college-womens-basketball",
- "mls",
- "premier-league",
- "la-liga",
- "serie-a",
- "bundesliga",
- "ligue-1",
- "champions-league",
- "nwsl",
- "ligamx-apertura",
- "ligamx-clausura",
- "copa-america",
- "club-world-cup",
- "world-cup",
- "concacaf-champions-cup",
- "concacaf-gold-cup",
- "concacaf-league"
-]New value: +[
+ "nfl",
+ "nba",
+ "wnba",
+ "mlb",
+ "nhl",
+ "college-football",
+ "college-basketball",
+ "college-womens-basketball",
+ "soccer",
+ "mls",
+ "premier-league",
+ "la-liga",
+ "serie-a",
+ "bundesliga",
+ "ligue-1",
+ "champions-league",
+ "nwsl",
+ "ligamx-apertura",
+ "ligamx-clausura",
+ "copa-america",
+ "club-world-cup",
+ "world-cup",
+ "concacaf-champions-cup",
+ "concacaf-gold-cup",
+ "concacaf-league",
+ "womens-world-cup",
+ "europa-league",
+ "euro-championship"
+]v1.17.5Input schema / properties / league / enumAdded value: +[
+ "nfl",
+ "nba",
+ "wnba",
+ "mlb",
+ "nhl",
+ "college-football",
+ "college-basketball",
+ "college-womens-basketball",
+ "mls",
+ "premier-league",
+ "la-liga",
+ "serie-a",
+ "bundesliga",
+ "ligue-1",
+ "champions-league",
+ "nwsl",
+ "ligamx-apertura",
+ "ligamx-clausura",
+ "copa-america",
+ "club-world-cup",
+ "world-cup",
+ "concacaf-champions-cup",
+ "concacaf-gold-cup",
+ "concacaf-league"
+]v1.14.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral burden well: it discloses that it returns source articles (not aggregated summaries) and flags the significant soccer special case (shared cross-competition feed, no competition-specific filter, tags preserved verbatim). It stops short of return-format or pagination detail, but the key behavioral quirk is surfaced.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, front-loaded with the core purpose and followed by the caveat. Every sentence carries information with no filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter read tool with no output schema, the description says what is returned and warns about the soccer special case, which is most of what an agent needs. It could say more about article shape or the missing competition filter for other leagues, but it is largely complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% (baseline 3), and the description genuinely adds meaning for the single 'league' parameter by explaining that league=soccer maps to a shared cross-competition feed with no per-competition filtering. This is useful semantic guidance beyond the enum itself.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Returns source news articles') scoped to a Yahoo Sports league, so an agent can tell what it fetches. However, it does not differentiate itself from close siblings like yahoo_sports_topic_news or yahoo_sports_more_news, so the boundary is left to inference.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit statement of when to use this tool versus alternatives such as yahoo_sports_more_news or yahoo_sports_topic_news. The soccer note describes behavior, not a use/avoid condition, so the agent gets no routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.