Crawlora MCP

yahoo_shopping_home

Read-only

Fetch Yahoo Shopping homepage editorial cards, including title, link, category, and thumbnail. This is a buying-guide and deals feed, not product search; use yahoo_shopping_category for a section, yahoo_shopping_article for one guide, or yahoo_shopping_store for one retailer's offers.

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

Name	Required	Description	Default
`page`	No	1-based page number, defaults to 1

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 31, 2026

addedInput schema / properties

Added value: +{
+  "page": {
+    "description": "1-based page number, defaults to 1",
+    "type": "integer"
+  }
+}

First observedOct 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

The annotations already declare readOnlyHint and openWorldHint. The description adds useful behavioral context by framing the resource as a buying-guide and deals feed rather than product search, and by noting the editorial card fields, though it does not discuss pagination or freshness.

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 sentences with no wasted text. The core purpose is front-loaded, and the alternatives are clearly appended as routing guidance.

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

Completeness5/5

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

With annotations covering safety and an output schema present, the description gives enough context for an agent to select this tool correctly. It clarifies the feed type and alternatives, so no critical selection information is missing.

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 fully documented in the schema. The description does not add any parameter-specific meaning beyond what the schema already provides, so the baseline of 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 states a specific verb and resource: fetching Yahoo Shopping homepage editorial cards, and lists the returned fields. It also explicitly distinguishes this homepage feed from product search and names the relevant sibling tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says when this tool is appropriate, clarifies that it is not product search, and routes the agent to yahoo_shopping_category, yahoo_shopping_article, or yahoo_shopping_store for adjacent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?