Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_entertainment_category

Fetch Yahoo Entertainment editorial stories by category (celebrity, movies, music, or tv) with pagination, returning titles, URLs, categories, and thumbnails.

Instructions

Yahoo Entertainment section story stream. Returns a Yahoo Entertainment section's editorial story feed: title, destination URL, category, and thumbnail image for each story, with page-based pagination. Sourced from Yahoo Entertainment's own server-rendered section pages.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page number, defaults to 1
categoryYesYahoo Entertainment section

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / category / enum
      Added value: +[
+  "celebrity",
+  "movies",
+  "music",
+  "tv"
+]
  2. Addedv1.14.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It explicitly discloses the output shape (title, destination URL, category, thumbnail), the page-based pagination model, and that data is sourced from Yahoo Entertainment's server-rendered section pages. It does not mention rate limits or auth, but this is a simple read-style feed and no destructive behavior is implied.

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?

Two tight sentences with no filler. The core purpose is front-loaded in the first sentence, and the second adds only high-value details: return fields, pagination, and source.

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 feed tool with no output schema and no annotations, the description covers the essentials: what is returned, how pagination works, and where data comes from. A slight gap is that it does not specify page size or behavior for out-of-range pages, but the schema's default page value covers the common case.

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%, so the schema already documents both parameters. The description reinforces that category selects a section and that pagination is page-based, but it does not add meaningful semantics beyond the schema.

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 states a clear action ('Returns') on a specific resource (Yahoo Entertainment section's editorial story feed) and lists the returned fields. It does not explicitly distinguish itself from sibling tools like yahoo_entertainment_home or yahoo_entertainment_article, so it stops short of full sibling differentiation.

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 usage context is implied: use this tool when you need a category-scoped story feed with pagination rather than a single article or homepage stream. However, it never names alternatives or states when not to use it, so the agent must infer the boundary from the name and description.

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