Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cvs_category

Retrieve product grid from any CVS OTC category, subcategory, or brand page, including prices, flags, and filterable facets.

Instructions

Browse a CVS OTC category page. Returns one page of a CVS.com OTC (over-the-counter) retail category, subcategory, or brand page's product grid: normalized products with title, brand, image, current/original price, and sponsored/featured/new-product flags; the total result count; and the facets (brand, color, size, price range, and other category-specific attributes, each with its selectable values and result counts) available to filter the page further. Covers the non-prescription retail catalog only. path is the segment of a page URL after "/shop/", e.g. "beauty" (top-level category), "health-medicine/allergy-sinus" (subcategory), or "brand-shop/s/safe-home" (brand page); a full https://www.cvs.com/shop/... URL or a "/shop/..." path is also accepted. Any of these can also carry an optional facet-filter suffix in the site's own URL shape, e.g. "beauty/makeup/eyes/q/CoverGirl/Black/brpc" to filter to brand CoverGirl and color Black -- see the response's facets field for which values/type codes a given category supports; filter values are case-sensitive exactly as the site renders them. page is a 1-indexed page number (default 1). sort is an optional result order matching the site's own Sort By control. CVS.com is only available from US/US-territory egress; a request from an unsupported region returns an upstream error rather than an empty result.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-indexed page number, default 1
pathYesCVS category, subcategory, or brand-page URL path, optionally with a /q/{value}/{typeCode} facet-filter suffix, e.g. \
sortNoResult sort order, default the site's own relevance order. One of pa (Price Low to High), pd (Price High to Low), tr (Top Rated), rc (Most Reviewed), az (Name A-Z), za (Name Z-A)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "pa",
+  "pd",
+  "tr",
+  "rc",
+  "az",
+  "za"
+]
  2. Addedv1.16.2

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries full burden and does so thoroughly. It details return contents (normalized products, flags, facets), input flexibility (URL segment, full URL, or /shop/ path), case-sensitivity of filter values, and the regional egress failure mode. This goes beyond basic expectations and gives concrete behavioral insight.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence serves a distinct purpose: scope, return payload, parameter formats, defaults, and a warning. It is front-loaded with the core purpose and returns, then progressively details inputs. No filler or redundancy; the length is justified by the complexity of the tool.

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 3-parameter tool without an output schema, the description is remarkably complete. It covers all required parameters, provides examples, explains sorting, and discloses the region limitation. An agent has everything needed to call the tool correctly and anticipate failure behavior, making it fully contextualized.

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

Parameters5/5

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

The schema descriptions are 100% covered, yet the description adds substantial value beyond them. It provides concrete examples for the path parameter ('beauty', 'health-medicine/allergy-sinus', 'brand-shop/s/safe-home'), explains the optional facet-filter suffix format, and fully decodes the sort enum codes (pa, pd, etc.). This ensures an agent understands exactly how to construct valid inputs.

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 clearly states the tool's function: 'Browse a CVS OTC category page' and specifies the exact resource types (category, subcategory, brand page) and what is returned (product grid, facets, total count). It also distinguishes from siblings by noting 'Covers the non-prescription retail catalog only,' which differentiates it from potential CVS product or category tools.

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 provides clear context for when to use the tool (for OTC retail catalog browsing) and includes a critical usage constraint: 'CVS.com is only available from US/US-territory egress.' However, it does not explicitly name sibling tools as alternatives or state when NOT to use them, which slightly weakens guidance compared to an explicit routing instruction.

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