Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

oldnavy_category

Browse an Old Navy, Gap, Banana Republic, or Athleta category to get subcategory breakdowns, product summaries with per-color inventory, and search facets with live counts.

Instructions

Browse an Old Navy, Gap, Banana Republic, or Athleta category. Returns a category/browse listing for one storefront category id (cid). cid is an opaque Gap Inc category id assigned by the storefront's own navigation -- neither oldnavy-search nor oldnavy-category currently surface a category-id list, so find one from the storefront's own category page URLs (the cid query parameter on a /browse/... page) for now. 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 cid was found under. Returns the category's subcategory breakdown, product summaries with per-color inventory data, and available search facets with live counts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidYesCategory id, from a storefront category page's own cid query parameter
pageNoOne-based page
brandNoStorefront to browse

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.5/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 disclose the return shape (subcategory breakdown, product summaries with per-color inventory, live facet counts) plus the constraint that cid is opaque and brand must match it. It does not mention auth requirements or rate limits, but for a read/browse operation the disclosed behavior is fairly rich.

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 purpose, then cid sourcing, brand mapping, and return shape. It is dense but each clause carries information; slightly long, but nothing is clearly wasted.

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?

No output schema exists, and the description compensates by describing what is returned. Combined with the cid-sourcing guidance and brand constraint, an agent has almost everything needed to call it, though pagination behavior for the page parameter is only implied.

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, but the description adds real meaning: it maps brand abbreviations (on/gap/br/at) to storefronts and states the default plus the matching constraint against cid. This is more than the schema conveys, lifting it above baseline.

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 ('Browse an Old Navy, Gap, Banana Republic, or Athleta category') and scopes it to one storefront category id. An agent can distinguish this from siblings like oldnavy_product, oldnavy_search, and oldnavy_categories without opening another schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly explains how to obtain the required cid ('find one from the storefront's own category page URLs ... the cid query parameter') and warns that neither oldnavy-search nor oldnavy-category currently surface a category-id list. It also states the brand must match the cid's storefront, which is exactly the routing guidance an agent needs.

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