Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

yahoo_shopping_sitemap

Read canonical Yahoo Shopping sitemap index, section archive, or date pages and return observed archive, monthly, day, or article links for crawling and link discovery.

Instructions

Yahoo Shopping sitemap archive or date page. Reads a canonical Yahoo Shopping sitemap index, section archive, or date page. Responses contain section archives, monthly archive links, day links, or article links depending on the page. Yahoo's date pages currently have broken previous/next links; this endpoint reports observed links and does not synthesize continuation.

Input Schema

NameRequiredDescriptionDefault
urlYesCanonical shopping.yahoo.com sitemap page URL from /yahoo-shopping/sitemaps or a prior response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.18

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the response shape varies by page type (section archives, monthly links, day links, article links) and warns that Yahoo's prev/next links are broken so no continuation is synthesized. That is exactly the kind of caveat an agent cannot get from schema fields. It stops short of describing pagination limits or failure behavior.

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, front-loaded with the purpose, then the input classes, then the response variability, then the broken-link caveat. No filler; only the first two sentences overlap slightly in restating what kinds of pages are read.

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 single-parameter, no-output-schema, unannotated crawl tool, the description covers what varies in the response and what known defect to expect. Missing only explicit routing to the sitemaps index tool as the starting point and any statement about error behavior on non-sitemap URLs.

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 url parameter already documents its provenance, so the schema does the heavy lifting. The description adds that acceptable URLs span index, section-archive, and date pages, which slightly widens understanding of valid inputs, but gives no format examples or validation rules.

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?

States a specific verb ('Reads') and resource ('Yahoo Shopping sitemap index, section archive, or date page'), and enumerates the page variants it handles. It does not explicitly name the sibling yahoo_shopping_sitemaps as the discovery entry point, so sibling differentiation is only implicit via the URL-provenance note.

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?

Usage is implied rather than stated: the schema says the URL must come 'from /yahoo-shopping/sitemaps or a prior response', which effectively tells the agent to start elsewhere. But the description itself never says when to use this versus yahoo_shopping_sitemaps or yahoo_shopping_article, and offers no exclusions.

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