Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

samsclub_product_related

Fetch related-item carousels for a Sam's Club product by its numeric product ID, returning shelves with prices, ratings, and images.

Instructions

Get a Sam's Club product's related items. Returns the related-item carousels shown on a Sam's Club product page, each a named shelf (e.g. "Members also considered", "Items you may like") of products with pricing, rating, and image. id is the numeric product id from a Sam's Club product page's /ip/ URL. An unrecognized id is not distinguished from a known one -- it still returns generic fallback shelves rather than an error.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric Sam's Club product id, from a product page's /ip/{slug}/{id} URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

A3.9/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 behavioral burden and does disclose a genuinely useful trait: an unrecognized id is not distinguished from a valid one and silently returns generic fallback shelves rather than an error. That error-handling caveat is exactly the kind of context annotations would not capture. Auth, rate-limit, and pagination behavior remain unstated, keeping it short of a 5.

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-loads the purpose, then layers return shape and the id-format note before the fallback caveat. Efficient and well ordered, though the id-format sentence partially duplicates the schema description, a small redundancy.

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 does the work of explaining the return value (named shelves of products with pricing, rating, and image) and covers the key edge case. For a single-parameter tool this is nearly sufficient; only broader behavioral traits like rate limiting are absent.

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% and the schema already documents id as a numeric product id from an /ip/{slug}/{id} URL. The description restates that same id format without adding new syntax or constraints, so the baseline 3 applies.

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 (Get) plus resource (a Sam's Club product's related items) and immediately clarifies the exact scope: the related-item carousels shown on a product page. This cleanly distinguishes it from siblings like samsclub_product or samsclub_departments without the agent needing to open the schema.

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 implied rather than stated: the description tells you what it returns but never says when to reach for it versus samsclub_product or the many other *_product_related siblings. No explicit when/when-not or alternative routing is provided, so it lands at the minimum viable level.

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