Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jcrew_product_reviews

Fetch one page of J.Crew or J.Crew Factory product reviews and overall rating summary by style ID and storefront, returning author, date, rating, headline, body, and verified status.

Instructions

Get reviews for a J.Crew or J.Crew Factory product. Returns one page of a product's customer reviews (author, location, date, rating, headline, body, and verified-purchase flag), plus the product's overall rating summary (average rating, rating count, per-star histogram, and recommended ratio). pid is a style id (e.g. CX415), as returned by jcrew-search's products[].id field. site must match the storefront the pid belongs to (default jcrew). A product with no reviews yet, or a well-formed but unrecognized pid, returns a well-formed empty result, not an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pidYesStyle id, from a search result's id field
pageNoOne-based page, 10 reviews per page
siteNoStorefront the pid belongs to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / site / enum
      Added value: +[
+  "jcrew",
+  "factory"
+]
  2. Addedv1.16.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It clearly states the return data includes author, location, date, rating, headline, body, verified-purchase flag, and overall rating summary. It also proactively discloses edge cases: empty results for no reviews or unrecognized pid, and that it returns one page at a time. This is transparent and goes beyond basic expectations.

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 well-structured with a clear opening sentence, then details on return content, parameter usage, and error handling. It is detailed but not verbose, with each sentence contributing value. Front-loaded with the purpose and return data.

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?

Despite no output schema, the description thoroughly explains the return data fields and rating summary. It covers error handling and pagination. For a reviews tool, this is comprehensive. It could mention if there is any sorting or filter options, but those are not in the schema, so it is complete enough.

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 description adds clarification for pid (style id, example CX415) and site (must match storefront). It does not add meaning for page parameter beyond what the schema defines (one-based page, 10 per page), but the schema already covers it. The baseline of 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?

The description states a specific verb ('Get reviews'), a resource ('a J.Crew or J.Crew Factory product'), and clearly differentiates it from siblings by specifying it returns customer reviews and rating summaries. It distinguishes from other product-related tools like jcrew_product and jcrew_search by focusing on reviews and rating data.

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?

The description provides clear context on when to use it (to fetch reviews for a product identified by pid) and specifies that pid comes from jcrew-search's products[].id field, and that site must match the storefront. It does not explicitly mention alternatives or when not to use it, but the sibling tools like jcrew_product and jcrew_search are distinct enough that implicit guidance is adequate.

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