Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cvs_search

Find non-prescription CVS products by keyword and retrieve their prices, images, and filterable facets in structured JSON.

Instructions

Search CVS OTC products by keyword. Performs a keyword search across CVS.com's non-prescription retail/OTC catalog and returns one page of results: 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 attributes, each with its selectable values and result counts) available to filter the results further. This is the same product-search backend cvs-category reads, just reached by keyword instead of by category/brand path. Covers the non-prescription retail catalog only. q is the search keyword or phrase, required. page is a 1-indexed page number (default 1). sort is an optional result order matching cvs-category's own Sort By values. 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
qYesSearch keyword or phrase
pageNo1-indexed page number, default 1
sortNoResult sort order, default relevance. 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.1/5.0
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that it returns one page of results with normalized products, total count, and facets, plus the egress limitation: 'a request from an unsupported region returns an upstream error rather than an empty result.' It also notes it covers non-prescription retail only. It doesn't mention pagination limits or rate limits, but covers key behaviors.

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?

The description is well-structured with a front-loaded purpose, then return details, backend relation, scope, and egress note. It's slightly verbose with some redundancy (e.g., 'Search CVS OTC products' and 'Performs a keyword search across CVS.com's non-prescription retail/OTC catalog'), but overall efficient.

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?

Given no output schema and no annotations, the description covers return structure (products, facets, total count), scope, pagination via page, and error behavior for region. It doesn't describe output schema but that's not required since no output schema exists. It's comprehensive for a search tool.

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% with each parameter described. The description adds minor context: q is required (already in schema), page is 1-indexed (already in schema), and sort matches cvs-category's values (already in enum descriptions). Thus it adds little beyond schema, so baseline 3.

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 'Search CVS OTC products by keyword' and details the return payload. It distinguishes itself from sibling cvs-category by noting it's the same backend reached by keyword instead of category/brand path.

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?

It explicitly contrasts with cvs-category: 'same product-search backend cvs-category reads, just reached by keyword instead of by category/brand path.' It also scopes to non-prescription retail catalog only, implying when not to use (prescription items). However, it doesn't enumerate all alternative search tools, so not a full when-not list.

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