Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kohls_product_reviews

Retrieve paginated customer reviews for a Kohl's product using its web_id, including ratings, text, reviewer details, dates, and photo URLs.

Instructions

Browse a Kohl's product's customer reviews. Returns one page of a Kohl's product's customer reviews (title, text, rating, secondary ratings such as quality/durability/value/style, reviewer name and location, submission date, and photo URLs). web_id is the same identifier a GET /kohls/category response's products[].web_id field carries. A web_id with zero reviews returns a genuine zero-result response rather than an error.

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, 10 reviews per page (default 1)
web_idYesKohl's product web id, e.g. from a GET /kohls/category response's products[].web_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A3.7/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 meaningfully disclose behavior: one page per call (pagination), the returned field set, and especially that a web_id with zero reviews yields a genuine zero-result rather than an error. It omits sort order, total counts, and any rate/auth notes, so it is strong but not exhaustive.

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?

Three sentences, front-loaded with the purpose, then return payload, then the zero-result edge case. The field enumeration is somewhat long but justified because there is no output schema. No wasted filler.

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?

With no output schema, the description usefully enumerates the return fields and covers pagination and the empty-result edge case, which is what an agent needs to call it correctly. Missing only minor behavioral detail like ordering/counts.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents both page and web_id. The description's restatement of web_id provenance (GET /kohls/category products[].web_id) duplicates what the schema property description already says, adding little beyond it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Browse') and resource ('a Kohl's product's customer reviews'), and enumerates the returned fields. It clearly signals a distinct reviews endpoint, though it does not need or provide sibling differentiation (no other review tool exists for Kohl's).

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

Usage Guidelines3/5

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

Usage is only implied: it hints where web_id comes from (a GET /kohls/category response) and that a zero-review web_id returns a zero-result, but it never states when to call this versus kohls_category or other sibling endpoints. No explicit when/when-not guidance.

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