Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_news_related

Fetch related Yahoo News articles for a given article ID, returning Yahoo's recommended items with cursor-based pagination.

Instructions

Yahoo News related articles. Returns a page of articles Yahoo recommends alongside a given article -- the "you may also like" strip at the bottom of an article page -- with cursor-based pagination. Sourced from Yahoo's own recommendation gateway.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of related articles to return, default 10, clamped to 1..50
cursorNoPagination cursor from a previous response's next_cursor
content_idYesArticle id (the id field returned by home/category/article)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It mentions pagination via cursor and that results come from Yahoo's recommendation gateway, but does not specify the return structure (e.g., fields like title, URL) or any rate limits. It adds some context but lacks depth.

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 two sentences with zero waste. It front-loads the core purpose (returns related articles) and packs pagination and data source into a second sentence. Every word earns its place.

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?

Given the tool's complexity (pagination, multiple parameters) and the lack of an output schema, the description could benefit from noting expected response fields or any potential errors. However, it is adequate for a simple recommendation tool with well-documented parameters.

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 parameters are fully documented in the schema. The description adds some context by explaining content_id as an article id and mentioning cursor-based pagination, but does not go beyond what the schema already states.

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 clearly states the tool returns a page of related articles recommended by Yahoo, referencing the 'you may also like' strip. It specifies the verb 'returns' and the resource 'related articles', and distinguishes it from generic article fetchers by focusing on recommendations.

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 implies usage: given an article's content_id, you get related articles. It does not explicitly state when not to use this tool or mention alternatives (e.g., yahoo_news_article for fetching an article itself). However, the context makes the intended use clear enough.

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