Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

oldnavy_product

Fetch normalized product details for an Old Navy, Gap, Banana Republic, or Athleta color variant by its color-specific pid, including images, rating, and per-size priced offers.

Instructions

Get an Old Navy, Gap, Banana Republic, or Athleta product. Returns normalized product-detail data for one color variant: name, description, images, aggregate rating, and every size offered in that color as a separate priced offer. pid is a color-specific product id, as returned by oldnavy-search's product colors[].id field (not the bare base product id). 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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pidYesColor-specific product id, from a search result's colors[].id field
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 full behavioral burden and largely succeeds: it discloses that the tool returns one color variant, lists the exact return fields, explains that sizes appear as separate priced offers, and notes the brand-matching constraint. It doesn't cover errors or rate limits, but for a read-only product-detail tool this is solid transparency.

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 three sentences with no filler: it front-loads the product/tool purpose in sentence one, then adds the critical pid and brand usage details. Every sentence earns its place, though it is slightly dense.

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 2-parameter tool with no output schema and no annotations, the description covers the essentials: return content, input provenance, brand handling, and default. Minor gaps exist (exact response structure, error behavior), but nothing critical is missing for correct invocation.

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 meaning beyond the schema by explaining that pid is color-specific and sourced from colors[].id, and by mapping brand enum codes ('on', 'gap', 'br', 'at') to storefront names plus the default. This is meaningful added semantics.

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 and resource ('Get an Old Navy, Gap, Banana Republic, or Athleta product') and immediately states the return scope: normalized product-detail data for one color variant with named fields. This clearly distinguishes it from siblings like oldnavy_search, oldnavy_product_availability, and oldnavy_product_reviews.

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 operational guidance: pid comes from oldnavy-search's colors[].id field, warns against using the bare base product id, and instructs that brand must match the brand the pid was found under. It doesn't explicitly name 'when not to use' alternatives, but the usage context is strong.

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