Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

nike_product_reviews

Fetch a Nike product's customer reviews and aggregate rating summary, including average score and star breakdown, using its slug and style-color ID.

Instructions

Get Nike product reviews. Returns one page of a Nike product's customer reviews, plus an aggregate rating summary (average rating and a per-star rating breakdown) that Nike's own product-detail endpoint does not otherwise expose. slug and style_color are the same values nike-product accepts (from a search result's colors[].slug/colors[].style_color fields). A product with no reviews yet returns a well-formed empty result rather than an error. Requesting a page beyond the available result pages returns a not-found error.

Input Schema

NameRequiredDescriptionDefault
pageNoOne-based page number, defaults to 1
slugYesProduct-detail URL slug, from a search result's colors[].slug field
style_colorYesStyle-color id, from a search result's colors[].style_color field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A4.1/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 a good job: it discloses the return shape (one page + aggregate summary), that empty-review products yield a well-formed empty result rather than an error, and that out-of-range pages return a not-found error. It omits auth requirements and rate limits, keeping it short of a 5.

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?

Front-loaded with the purpose and return content, followed by parameter sourcing and then two edge-case behaviors. Every sentence adds value, though the density is high and the parameter sourcing sentence partially duplicates the schema.

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 tool with no output schema and no annotations, the description covers return contents and the two most likely failure modes (empty reviews, out-of-range page). Missing details about additional failure conditions or auth keep it from being fully complete.

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%, so the schema already documents page, slug, and style_color including their sourcing from colors[].slug/style_color. The description largely restates that mapping and adds only the linkage note that these are the same values nike-product accepts, so 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 and resource ('Get Nike product reviews') and immediately scopes the return content to one page plus an aggregate rating summary. It distinguishes itself from the sibling nike_product by noting the summary data that the product-detail endpoint does not expose.

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?

It clearly positions the tool relative to nike-product by explaining that slug/style_color come from the same values that tool accepts (via colors[].slug/style_color). However, it never states an explicit 'use this instead of nike_product when you want reviews' rule, so guidance is strong but not fully spelled out.

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