Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kroger_category

Retrieve Kroger category product listings and facets by providing slug and category ID, enabling pagination, sorting, and facet-based filtering.

Instructions

Browse a Kroger category. Browses a Kroger product category and returns normalized product cards plus facet groups, in the same shape as kroger-search. slug and category_id together identify the category (e.g. "pet" and "27" for kroger.com/pl/pet/27) -- call kroger-categories to discover every valid slug/category_id pair. Served from Kroger's own search JSON API using category_id as a taxonomy filter, with real upstream pagination; it falls back to parsing the rendered category page if that path is unavailable, and the source field reports which path answered. Facet filters and sort apply to the JSON path only: when any of them is set, a JSON-path failure returns an error rather than silently falling back to unfiltered results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoOne-based result page
slugYesCategory URL slug segment. Obtain valid slug/category_id pairs from kroger-categories
sortNoResult order. One of: relevance, name_asc, popularity_desc
scentNoComma-separated scent facet values
brandsNoComma-separated brand names to filter by, taken verbatim from a previous response's facets
flavorNoComma-separated flavor facet values
savingsNoComma-separated savings facet values
nutritionNoComma-separated nutrition/dietary facet values
price_maxNoUpper bound of the price filter; required to filter on price
price_minNoLower bound of the price filter; defaults to 0
category_idYesCategory numeric taxonomy id. Obtain valid slug/category_id pairs from kroger-categories
more_optionsNoComma-separated more-options facet values

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.17.5
    • changedInput schema / properties / category_id / description
      Previous value: -"Category numeric taxonomy id"New value: +"Category numeric taxonomy id. Obtain valid slug/category_id pairs from kroger-categories"
    • changedInput schema / properties / slug / description
      Previous value: -"Category URL slug segment"New value: +"Category URL slug segment. Obtain valid slug/category_id pairs from kroger-categories"
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "relevance",
+  "name_asc",
+  "popularity_desc"
+]
  2. Addedv1.16.2

TDQS

A4.6/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 full behavioral burden and does so exceptionally well. It discloses the underlying data source, real pagination, fallback to page parsing, the source field that reports which path answered, and the critical failure behavior when filters are set on a JSON-path failure.

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 dense but organized, front-loading purpose and then layering discovery, source behavior, fallback, and constraints. The only minor issue is a slight redundancy between the opening 'Browse a Kroger category' and the next sentence's 'Browses a Kroger product category,' but every other sentence earns its place.

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 12-parameter tool with no annotations and no output schema, the description is remarkably complete: it specifies output shape, how to obtain valid parameters, the underlying source, pagination, fallback behavior, and path-specific limitations. An agent has enough context to call this tool correctly and interpret its results.

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?

Since schema coverage is 100%, the baseline is 3, but the description adds meaningful semantic grouping beyond individual property docs: slug and category_id are jointly identifying, an example URL pattern is given, valid pairs come from kroger-categories, and facet/sort parameters have behavior tied to the JSON path. This elevates it above the 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?

The description opens with a specific verb and resource ('Browse a Kroger category') and immediately states the concrete output: 'normalized product cards plus facet groups.' It also names sibling tools and clarifies its relationship to them, particularly by directing users to kroger-categories for valid slug/category_id pairs and stating that output shape matches kroger-search.

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 clearly explains that slug and category_id must be used together and tells the agent to call kroger-categories to discover valid pairs, which is actionable guidance. It also gives an important usage caveat about facet filters and sort applying only to the JSON path, but it does not explicitly state when to choose this tool over kroger-search beyond the implied category-browsing context.

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