Crawlora MCP

yahoo_autos_category

Read-only

Fetch a Yahoo Autos section's paged story feed. Use yahoo_autos_home for homepage picks or yahoo_autos_article to retrieve one discovered story's content.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category": "<category>"
    },
    "name": "yahoo_autos_category"
  }
}

Input Schema

Name	Required	Description	Default
`page`	No	1-based page number, defaults to 1
`category`	Yes	Yahoo Autos section. Documented values: auto-shows, classic-and-collector, deals-and-buying-guides, ev-and-future-tech, general, new-vehicles-and-reviews, ownership, people-and-culture, policy-and-environment, safety-and-recalls.

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.

Changed2 schema fields changedOct 7, 2026

addedInput schema / properties / category / description

Added value: +"Yahoo Autos section. Documented values: auto-shows, classic-and-collector, deals-and-buying-guides, ev-and-future-tech, general, new-vehicles-and-reviews, ownership, people-and-culture, policy-and-environment, safety-and-recalls."

addedInput schema / properties / page / description

Added value: +"1-based page number, defaults to 1"

First observedOct 5, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety/fetch profile is covered. The description adds only that the feed is 'paged', which is minor behavioral context and is already implied by the page parameter in the schema. No mention of ordering, page size, or empty-page behavior.

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, zero filler, with the core purpose front-loaded ahead of the sibling routing guidance. Every clause earns its place.

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?

An output schema exists, so return values need not be described. For a simple paged-feed fetch with a fully documented enum-style category parameter, the description plus structured fields are complete enough for correct invocation.

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 both parameters (page, category) are already documented, including the full list of category values. The description only implies 'section' maps to category and 'paged' maps to page, adding no syntax or constraints beyond the schema. Baseline 3 is appropriate.

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 (Fetch) and resource (a Yahoo Autos section's paged story feed), and explicitly names the two sibling tools it is not (yahoo_autos_home, yahoo_autos_article). An agent can distinguish this from the sibling category/home/article tools without opening schemas.

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?

Names both alternatives with the condition that selects each: yahoo_autos_home for homepage picks and yahoo_autos_article for a single discovered story's content. This leaves little to inference about when to route here versus elsewhere.

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?