Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_autos_category

Fetch Yahoo Autos editorial stories by section and page, returning titles, URLs, categories, and thumbnails for each item. Use it to build paginated category feeds from Yahoo Autos.

Instructions

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

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

NameRequiredDescriptionDefault
pageNo1-based page number, defaults to 1
categoryYesYahoo Autos section

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / category / enum
      Added value: +[
+  "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"
+]
  2. Addedv1.14.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations present, the description carries the behavioral disclosure burden. It discloses page-based pagination, the output fields per story, and the data source (server-rendered section pages), which provides useful context beyond a bare 'returns feed' statement. It does not mention ordering or rate limits, but these are minor for a simple read-only feed.

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?

The description is compact at two sentences and front-loads the main purpose. The first sentence is somewhat redundant with the second ('section story stream' vs. 'section's editorial story feed'), so it is not perfectly efficient, but it remains tightly written.

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?

For a simple two-parameter feed tool with no output schema, the description is complete: it identifies the required category input, the optional page behavior, the per-item output fields, and pagination. An agent has enough information to select and invoke this tool correctly.

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%: both 'category' and 'page' have descriptions, and 'category' has a full enum. The tool description adds little parameter meaning beyond calling the category a 'section,' so the baseline score 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 uses a specific verb ('Returns') with a clear resource ('a Yahoo Autos section's editorial story feed') and enumerates the feed's contents (title, destination URL, category, thumbnail). This clearly distinguishes it from sibling tools like yahoo_autos_article and yahoo_autos_home.

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 this is the tool for fetching a Yahoo Autos section's story feed, but it never explicitly states when to use it versus alternatives such as yahoo_autos_article or yahoo_autos_home. There are no exclusions or alternative recommendations.

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