Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanatics_search

Search Fanatics' product catalog by keyword to get product names, brands, prices, availability, images, and URLs. Sort by top sellers, price, or newest arrivals and control page size.

Instructions

Search Fanatics' product catalog. Returns one page of Fanatics' own keyword search results (name, brand, price, availability, image, url).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoOne of TopSellers, LowestPrice, HighestPrice, NewestArrivals. Defaults to TopSellers.
queryYesFree-text search keywords.
page_sizeNoResults per page. One of 24, 48, 72. Defaults to 24.
page_numberNo1-based result page. Defaults to 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It adds value by disclosing that results are limited to one page and lists the returned fields (name, brand, price, availability, image, url). However, it omits details about error handling, rate limits, or how pagination works beyond the schema's parameter descriptions.

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 a single, front-loaded sentence with no wasted words. It immediately states the tool's purpose (Search Fanatics' product catalog), then specifies the output shape. Every element earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

In the absence of an output schema and annotations, the description provides the returned field names and the one-page limitation. It is adequate for a simple search tool but does not cover potential behavioral nuances like sorting semantics, default values (already in schema), or expected response structure beyond field names.

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?

The input schema provides complete descriptions for all four parameters (query, sort, page_size, page_number), so coverage is 100%. The description adds no parameter-level meaning beyond what the schema already states, leading to the baseline score of 3.

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?

The description states a specific verb ('Search') and resource ('Fanatics' product catalog'), and clarifies that it returns one page of Fanatics' own keyword search results. It clearly communicates what the tool does, though it doesn't explicitly name sibling tools to differentiate itself from them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. The description implies it should be used for keyword searching Fanatics products, but it offers no exclusions or comparisons to related Fanatics tools (e.g., fanaticscollect_auctions, fanaticslive_show).

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