Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bestbuy_category

Fetch a Best Buy category's product listing by category ID, returning up to 24 items per page with SKU, title, URL, image, price, rating, and review count. Use optional page to browse further.

Instructions

Get a Best Buy category's product listing. Returns one page (up to 24) of one Best Buy category's product listing (sku, title, url, image, price, rating, review count). category_id is a Best Buy category id, e.g. pcmcat138500050001, found in a category page URL's trailing .c?id= segment. page is the optional 1-indexed page number (defaults to 1); requesting a page past the last one returns an empty products list, not an error.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "category_id": "<category_id>"
    },
    "name": "bestbuy_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-indexed page number, defaults to 1
category_idYesBest Buy category id

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 burden and does well: it discloses the page size cap (up to 24), the exact fields returned, and the important edge-case behavior that an out-of-range page returns an empty products list rather than an error. Auth/permission behavior is not covered, keeping it from 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-loaded with the core purpose followed by return contents and parameter details, so an agent can act after the first sentence. Slightly marred by redundancy, repeating 'Best Buy category's product listing' in the opening two clauses.

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?

No output schema exists, but the description compensates by listing the returned fields. Combined with both parameter explanations and the pagination edge case, it is complete for a two-parameter listing tool, with only auth/rate-limit context missing.

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 100%, so the 3 baseline applies, but the description adds genuine value beyond the schema: it gives a concrete category_id example (pcmcat138500050001) and explains where to find it in a URL, plus confirms page is 1-indexed with a default of 1.

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: 'Get a Best Buy category's product listing', and enumerates the returned fields (sku, title, url, image, price, rating, review count). It clearly distinguishes browsing a category's products from fetching a single product or searching, though it does not name sibling tools explicitly.

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 how-to-locate-category_id note tells the agent the tool is for browsing a known category, but there is no explicit when-to-use versus bestbuy_search, bestbuy_categories, or bestbuy_product routing guidance.

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