Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kohls_category

Browse a Kohl's category or curated campaign page to retrieve page-one product grids, pricing, availability, and facets, then use facet category values to discover and drill into the catalog taxonomy.

Instructions

Browse a Kohl's category or curated campaign page. Returns a Kohl's category or curated campaign page's product grid (page 1 only), with products (title, image, colors, pricing, rating, availability) and facets for discovering further category values. category is Kohl's own catalog taxonomy string, e.g. "Room:Dorm" or "Department:Kitchen & Dining" -- combine multiple dimensions with a literal "+", percent-encoded as "%2B" so it survives as "+" rather than being decoded to a space (e.g. "Room%3ADorm%2BDepartment%3ABedding"). Every facets[].options[].category value in a response is a ready-to-use category string for a follow-up call, so a caller can discover the full taxonomy by starting from a known category (e.g. "Room:Dorm") and following facets. A category value Kohl's does not recognize returns a 404 rather than an unfiltered listing; a recognized dimension with no matching products returns a genuine zero-result response instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryYesKohl's catalog taxonomy string, e.g. \

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the disclosure burden well: it states that only page 1 of the product grid is returned, lists the product fields and facets included, and distinguishes a 404 for an unrecognized category from a genuine zero-result response for a valid empty category. These are exactly the behavioral traits an agent needs before calling a browse endpoint.

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 front-loaded with purpose and return behavior, then moves into encoding and error semantics, so no sentence is wasted. It is somewhat dense and technical, but the density is justified for a one-parameter tool with no annotations and no output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter browse tool with no output schema and no annotations, the description supplies enough context to call it correctly: return shape, page limitation, facet discovery behavior, category encoding, and the 404 versus zero-result distinction are all covered.

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

Parameters5/5

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

Although the schema formally covers the single required parameter, its description is truncated, so the tool description adds essential semantics: category is Kohl's catalog taxonomy, uses examples like 'Room:Dorm' and 'Department:Kitchen & Dining', and explains combining dimensions with a literal '+' that must be percent-encoded as '%2B'. It also explains that facet option values are ready-to-use category strings, which is substantial guidance beyond the schema.

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: 'Browse a Kohl's category or curated campaign page,' and immediately states that it returns a category page's product grid. That makes its scope clear enough to distinguish it from product-detail, store-locator, or suggestion siblings.

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 gives clear usage context by explaining that the tool returns page 1 of a category or campaign page and that facets can be followed to discover further taxonomy values. However, it does not explicitly name alternatives such as kohls_suggest, kohls_product_reviews, or kohls_stores, so the when-not-to-use guidance is only implicit.

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