Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

oldnavy_product_reviews

Fetch paginated customer reviews and overall rating summaries for Old Navy, Gap, Banana Republic, or Athleta products using a color-specific product id.

Instructions

Get reviews for an Old Navy, Gap, Banana Republic, or Athleta product. Returns one page of a product's customer reviews (author, 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 color-specific product id, as returned by oldnavy-search's product colors[].id field (not the bare base product id) -- the same pid oldnavy-product accepts. Select the storefront with the brand parameter (on for Old Navy, gap for Gap, br for Banana Republic, at for Athleta; defaults to on) -- it must match the brand the pid was found under. A product with no reviews yet returns a well-formed empty result, not an error.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pidYesColor-specific product id, from a search result's colors[].id field
pageNoOne-based page, 10 reviews per page
brandNoStorefront the pid belongs to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / brand / enum
      Added value: +[
+  "on",
+  "gap",
+  "br",
+  "at"
+]
  2. Addedv1.14.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden. It states that it returns one page of reviews, the default brand, and that a product with no reviews returns a well-formed empty result rather than an error. It does not cover auth, rate limits, or side effects, but for a read-only reviews tool these are minimal. The disclosed behavior is genuinely useful.

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 moderately sized and front-loaded with the core purpose, then elaborates on parameters and edge cases. Every sentence adds information; it could be slightly trimmed but is well-structured and not bloated.

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 3-parameter tool with no output schema, the description covers the essential operation: what is returned, how to pick the pid and brand, and the empty-result behavior. Pagination and page specifics are left to the schema, which is sufficient. Nothing critical for calling it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful guidance beyond the schema: it clarifies that pid is color-specific and not the base product id, explains the brand enum values, and notes the default. It also ties pid to the oldnavy-search output, which is valuable for correct invocation.

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') and a clear resource (product reviews for four brands). It enumerates exactly what is returned (review fields and rating summary), which differentiates it from sibling tools like oldnavy_product or oldnavy_search. The purpose is unmistakable.

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 gives clear context: it explains the pid requirement and the brand constraint, and notes that pid is the same as oldnavy-product accepts, implicitly distinguishing it from product-detail tools. However, it does not explicitly mention 'when not to use' or point to alternative tools for other needs (e.g., availability), so it falls short of a 5.

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