Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_shopping_home

Fetch Yahoo Shopping's homepage editorial story feed with titles, links, categories, and thumbnails, paginated by page number for shopping guide and deals content research.

Instructions

Yahoo Shopping homepage story stream. Returns Yahoo Shopping's homepage editorial story feed: title, destination URL, category, and thumbnail image for each story. Page follows Yahoo's own path-segment pagination. This is Yahoo's shopping buying-guide/deals content site, not a product-results API.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "yahoo_shopping_home"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number, defaults to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.18
    • addedInput schema / properties / page
      Added value: +{
+  "description": "1-based page number, defaults to 1",
+  "type": "integer"
+}
  2. Addedv1.14.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries full disclosure burden. It discloses the returned fields and the unusual pagination model ('path-segment pagination'), which is useful. But it says nothing about how many stories a page holds, ordering, or whether the feed is finite — practical traits an agent needs to page correctly.

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?

Four short sentences, with the core purpose front-loaded and the disambiguation last. There is minor redundancy between 'homepage story stream' and 'homepage editorial story feed', but nothing that wastes meaningful space.

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?

There is no output schema, and the description compensates by naming the four returned fields. For a zero-required-parameter feed tool the definition is nearly sufficient; only pagination limits and feed ordering remain unstated.

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% and the single 'page' parameter is already documented as 1-based defaulting to 1. The description adds only the note that pages follow Yahoo's path-segment scheme, which marginally enriches the schema but doesn't clarify upper bounds or behavior past the last page.

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?

States a specific verb+resource ('Returns Yahoo Shopping's homepage editorial story feed') and enumerates the payload fields (title, destination URL, category, thumbnail). The closing sentence explicitly distinguishes it from a product-results API, which separates it from the many yahoo_shopping_* siblings.

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?

The final sentence gives a clear when-not ('not a product-results API'), steering agents away from using it for product lookups. It stops short of naming the sibling to use instead (e.g., yahoo_shopping_category or yahoo_shopping_store), so routing still requires inference.

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