Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanaticscollect_trending_searches

Retrieve Fanatics Collect's trending search terms from its public GraphQL API. Get the same list shown in the site's header search box, without credentials.

Instructions

Get Fanatics Collect trending search terms. Returns Fanatics Collect's own currently trending search terms -- the same list shown in the site's own header search box before the visitor types anything. Credential-free public data from Fanatics Collect's own GraphQL API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of terms to return, 1-50, default 8

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.2/5.0
Behavior4/5

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

Annotations are absent, so the description must cover behavior. It mentions credential-free and public, which sets expectations about authentication and access. It also notes the data comes from the site's own header search box, giving context on the data's origin. However, it doesn't disclose potential rate limits or the exact format of the response, but given no annotations, this is fairly thorough.

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 concise, two sentences, with the key information front-loaded. It avoids redundancy and each sentence adds value.

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?

Given the tool has only one optional parameter and no output schema, the description provides adequate context: what it returns, its public nature, and its source. It lacks explicit return format details, but the simplicity of the tool makes that less critical. Nearly complete for a simple tool without annotations.

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 schema covers 100% of the parameter (limit) with a clear description of its range and default. The description doesn't add additional information about the parameter, but the schema is sufficient, so a baseline of 3 is appropriate.

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 clearly states the tool fetches Fanatics Collect's own currently trending search terms, contrasting with other search tools. It is specific about the source and what 'trending' means in this context, distinguishing it from generic search or trending tools.

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?

The description implies usage by specifying this is credential-free public data, but doesn't explicitly state when to use this vs alternatives like 'goat_trending_searches' or 'stubhub_trending'. However, the context is clear enough for an agent to infer this is for Fanatics Collect trend data specifically.

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