Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanatics_category

Fetch product listings from a Fanatics league or team category, returning name, brand, price, availability, image, and URL for each item.

Instructions

Browse a Fanatics league or team category. Returns one page of a Fanatics league or team category's product listing (name, brand, price, availability, image, url). Use GET /fanatics/categories to discover valid category urls.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesA fanatics.com league or team category URL, exactly as returned by a fanatics_categories result's url field.
sortNoOne of TopSellers, LowestPrice, HighestPrice, NewestArrivals. Defaults to TopSellers.
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.9/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 burden. It discloses that the tool returns one page of product listing data and enumerates the returned fields, which is useful. It does not mention read-only guarantees, error behavior, or rate limits, but 'Browse' and 'Returns' imply a safe read operation.

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?

Three sentences with no filler, and the core purpose is front-loaded. The phrase 'Fanatics league or team category' is repeated several times, making it slightly less tight than ideal, but the overall structure is 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?

The description gives the input source, notes pagination, and lists output fields, which is sufficient for a simple browse tool given that the schema fully documents parameters. It could add more about error or edge-case behavior, but nothing critical is missing for basic invocation.

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 schema already documents all four parameters. The description reinforces that the url must come from fanatics_categories, but this is also stated in the schema, so the description adds no new parameter-level meaning.

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 states a specific action ('Browse'), a specific resource ('Fanatics league or team category'), and what is returned (product listing fields). It also distinguishes itself from category discovery by pointing to GET /fanatics/categories for valid category URLs.

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 clearly explains the prerequisite for obtaining a valid category URL by directing the agent to fanatics_categories. It does not explicitly contrast with sibling tools like fanatics_product or fanatics_search, but the category-listing scope is clear enough for basic routing.

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