Crawlora MCP

fanatics_search

Read-only

Search Fanatics' public product catalog by free-text query and return one page of product results with name, brand, price, availability, image, and URL. Use page_number, page_size, and sort to navigate; use fanatics_product for one item or fanatics_category to browse a category.

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": {
      "query": "<query>"
    },
    "name": "fanatics_search"
  }
}

Input Schema

Name	Required	Description
`sort`	No	One of TopSellers, LowestPrice, HighestPrice, NewestArrivals. Defaults to TopSellers.
`query`	Yes	Required. Free-text search keywords, e.g. 'colts jersey'.
`page_size`	No	Results per page. One of 24, 48, 72. Defaults to 24.
`page_number`	No	1-based result page. Defaults to 1.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the paging framing ('return one page') and lists result fields, but those fields and the page/sort parameters are already spelled out in the input and output schemas, so the marginal behavioral content is modest.

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?

Two sentences, zero filler, with the core action and scope front-loaded ahead of the routing guidance. Every clause maps to a distinct piece of information an agent needs.

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

Completeness5/5

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

With 100% schema coverage, an output schema, and annotations covering safety and open-world behavior, the description only needs to establish scope and routing, which it does. Nothing required to invoke the tool correctly is missing.

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%, including the sort enum values and page_size constraints, so the schema does the heavy lifting. The description only repeats that page_number, page_size, and sort are used to navigate, adding no new syntax or format meaning beyond the schema.

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?

States a specific verb and resource ('Search Fanatics' public product catalog by free-text query') and scopes the output to one page of product results. It explicitly distinguishes itself from fanatics_product and fanatics_category, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Names both alternatives and the condition that selects them: fanatics_product for a single item, fanatics_category for browsing a category, and this tool for free-text search. Nothing about selection is left to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?