Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

costco_search

Search Costco products by text query or category, returning titles, brands, models, images, and ratings; query-only searches may return partial sitemap results if primary access is blocked.

Instructions

Search Costco products. Returns public Costco products matching a text query and/or a category slug: title, brand, model, image, and rating for each result. GDX is primary; if GDX is blocked, query-only searches may return explicitly partial product-sitemap results.

Input Schema

NameRequiredDescriptionDefault
queryNoSearch text
categoryNoCostco category slug, e.g. the last path segment of a category page URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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 disclosure burden, and it does add real behavioral context beyond the schema: it names the primary data source (GDX) and warns that query-only searches may return explicitly partial product-sitemap results when GDX is blocked. It still omits result limits, pagination, and sort behavior, which matters for a search 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?

Three sentences, front-loaded with purpose, then return shape, then the fallback caveat. No filler; the only mild density is the compressed GDX/sitemap sentence, which still earns its place by flagging partial results.

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?

Because there is no output schema, the description correctly compensates by listing returned fields, and it covers the degraded-mode behavior. For a two-optional-parameter search tool the remaining gaps (pagination, result caps) are minor but not negligible.

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 coverage is 100% and both parameters are documented in the schema, so the baseline is 3. The description only adds the combinability semantics ("and/or"), without elaborating on query syntax, matching behavior, or how a category slug interacts with a text query.

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 and resource ("Search Costco products") and enumerates the returned fields (title, brand, model, image, rating), which makes the result type concrete. It does not explicitly distinguish itself from costco_categories (browse) or costco_product (detail lookup), so routing among the Costco siblings is left to inference.

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 "query and/or a category slug" phrasing implies how to combine parameters, but the description never says when to prefer this over costco_categories for browsing or costco_product for a known item. Usage is implied rather than stated, with no exclusions or named alternatives.

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