Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

samsclub_category

Browse a Sam's Club category or collection by numeric id or /browse URL, returning paginated product grid data with pricing, availability, rating, and images.

Instructions

Browse a Sam's Club category or collection. Returns a Sam's Club category or collection page's product grid, with real page-based pagination. id accepts a bare numeric category id (from a nav link's /browse/{id} URL) or a full /browse/{slug}/{id} URL copied from samsclub.com -- only the trailing id is used. Returns products with name, brand, pricing, availability, rating, and image. An id samsclub.com does not recognize returns a genuine zero-result response rather than an error.

Input Schema

NameRequiredDescriptionDefault
idYesSam's Club category id, or a /browse/{slug}/{id} URL
pageNoResult page, 1-based, defaults to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden well: it discloses page-based pagination, that only the trailing id of a URL is used, and that an unrecognized id returns a genuine zero-result response rather than an error. That error-behavior disclosure is a meaningful, non-obvious trait, though auth/rate-limit context is absent.

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?

Four sentences, front-loaded with purpose then id handling then return shape then edge-case behavior. Each sentence adds distinct information with little redundancy, though it is slightly verbose.

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 compensates by enumerating returned product fields (name, brand, pricing, availability, rating, image) and covering pagination and the unrecognized-id case. It is largely complete for an agent to invoke correctly.

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 already 100%, but the description adds real meaning beyond the schema: it explains that id accepts either a bare numeric id or a full /browse/{slug}/{id} URL and that only the trailing id is honored, plus notes the 1-based page default. This exceeds the baseline for fully-covered schemas.

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+resource ('Browse a Sam's Club category or collection') and clarifies it returns a product grid, which clearly separates it from product-detail or search siblings. However, it never explicitly contrasts itself with close siblings like samsclub_departments, so differentiation is inferred rather than stated.

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?

The description tells the agent where to source the id (a nav link's /browse/{id} URL) which is useful context, but it gives no explicit when-to-use vs alternatives guidance or exclusions relative to sibling tools. Usage is implied rather than directed.

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