Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanatics_search

Search Fanatics' product catalog by keywords to retrieve product IDs, names, brands, categories, prices, availability, images, and URLs, with sort and page controls.

Instructions

Search Fanatics' product catalog. Searches Fanatics products by the required query. Choose page_size (24, 48 or 72; default 24), page_number (default 1) and sort (TopSellers, LowestPrice, HighestPrice or NewestArrivals; default TopSellers). Each item has product id, name, brand, category, price, currency, availability, image and URL. Also returns total_items and has_next_page. An invalid page_size or sort returns 400.

Input 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

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 burden itself and does well: it discloses the return payload fields (id, name, brand, category, price, currency, availability, image, URL), the pagination metadata (`total_items`, `has_next_page`), and the failure mode (invalid page_size/sort returns 400). It doesn't mention auth or rate limits, but the behavioral surface is well covered.

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 purpose, then parameters, then return shape and error handling in four tight sentences. Slightly repetitive in re-listing option values already in the schema, but overall efficient with no wasted prose.

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?

For a 4-param search tool with no output schema, the description compensates by enumerating return fields, pagination metadata, and the 400 error condition. An agent has enough to call it correctly; only auth/rate-limit context is absent.

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 description coverage is 100%, so the baseline is 3. The description restates the enum values and defaults that the schema already documents, adding enumeration context but no genuinely new semantics beyond what the structured fields provide.

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 uses a specific verb+resource ('Search Fanatics' product catalog') and names the required `query`, so the agent immediately knows what the tool does. It does not, however, differentiate itself from siblings like `fanatics_product` or `fanatics_category`, which sit in the same product family.

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?

It states the required parameter and the valid option domains, which implies usage, but gives no explicit when-to-use guidance or exclusions relative to sibling tools such as `fanatics_category` or `fanatics_product`. The agent must infer that this is the free-text discovery entry point.

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