Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_sports_more_news

Fetch a paginated page from Yahoo Sports' public More News feed by page number, returning raw story fields; use topic news for topic-specific results.

Instructions

Yahoo Sports More News feed. Returns one page from Yahoo Sports' public More News feed using its page-number routes. Story items preserve the source fields as raw objects. The page exposes no server-side tag, sort, or topic filter; use yahoo-sports-topic-news for a topic-specific page.

Input Schema

NameRequiredDescriptionDefault
pageNo1-based Yahoo More News page number; defaults to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose that story items preserve source fields as raw objects (an important anomaly for agents expecting normalized fields), but it omits pagination behavior, when pages run out, and any auth or rate-limit context.

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 sentences, front-loaded with what the tool is, then the pagination mechanism, then the routing rule. Each sentence adds distinct information and the alternative is placed last where it matters least to correct invocation.

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 single optional-parameter feed tool with no output schema, the description covers the essential facts: one page per call, page-number addressing, raw item shape, and no filtering. The remaining gap is what happens past the last page or how many pages exist.

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 description coverage is 100% and the single `page` parameter is already documented as 1-based defaulting to 1. The description only restates that pages are addressed by page number, adding no syntax or range detail beyond the schema, so the baseline 3 applies.

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?

The description names a specific verb and resource ("Returns one page from Yahoo Sports' public More News feed") and scopes it to a page-number route, which makes it distinguishable from other Yahoo Sports news tools. It also names the sibling to use instead for topic-specific pages.

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 explicitly says the feed exposes no server-side tag, sort, or topic filter and routes topic needs to yahoo-sports-topic-news, which is clear when-to-use-else guidance. It does not distinguish itself from yahoo_sports_news or yahoo_sports_section_stream, which also return similar general feeds.

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