Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

yahoo_sports_topic_news

Fetch current article lists from any public Yahoo Sports root or sport-scoped topic page using a topic slug or full URL, returning articles with tags as embedded.

Instructions

Yahoo Sports topic news. Returns the current article list for a public Yahoo Sports root or sport-scoped topic page. Topic slugs are open-ended; article tags are returned exactly as Yahoo embeds them.

Input Schema

NameRequiredDescriptionDefault
topicNoOpen-ended root topic slug
topic_urlNoFull Yahoo Sports topic URL, including sport-scoped topic pages such as /golf/topic/lpga-tour/

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the pages are public, that the article list is current, and that article tags are returned exactly as Yahoo embeds them, but it does not cover pagination, error behavior, or what happens when no topic parameter is supplied.

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 description is short and front-loads the core behavior in the second sentence. The first sentence is largely a restatement of the tool name, but the remaining sentences are efficient and informative.

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

Completeness3/5

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

For a simple two-parameter news lookup, the description covers the resource type and gives some output nuance. However, with no annotations and no output schema, it should clarify what happens when neither optional parameter is provided and how topic versus topic_url selection works.

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 baseline is 3. The description adds only modest context—open-ended topic slugs and sport-scoped topic pages—most of which is already present in the schema descriptions; it does not explain the relationship between the two optional parameters or default behavior with no arguments.

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 resource and output type: it returns the current article list for a Yahoo Sports topic page, including root and sport-scoped topics. This is clear enough to distinguish a topic-news lookup from general Yahoo Sports news, though it does not explicitly name a sibling alternative.

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?

Usage is implied by the mention of root and sport-scoped topic pages, but there is no explicit guidance on when to use this versus yahoo_sports_news, yahoo_sports_more_news, or other Yahoo Sports news siblings. It also does not explain whether topic and topic_url are alternatives or whether one is preferred.

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