Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanaticscollect_trending_searches

Retrieve Fanatics Collect's current trending search terms to see what users are searching for before typing. Returns the same list shown in the site's header search box.

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.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates the data is 'currently trending' and mirrors the site header, but never states that this is a read-only, non-destructive operation, nor does it mention authentication, rate limits, or side effects.

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?

Two tight sentences that front-load the core action and then add useful context about the data source. No filler, though the second sentence partially restates the first in more detail.

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's simplicity (one optional parameter, no output schema, no annotations), the description is nearly complete: it states what is returned (trending search terms) and where it comes from. Minor gaps remain around return format (e.g., array of strings) and safety profile, but these are small for such a simple read operation.

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%; the single 'limit' parameter is fully documented in the schema (range 1-50, default 8). The description adds no additional parameter meaning, so a baseline 3 is appropriate.

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?

States a specific verb and resource ('Get Fanatics Collect trending search terms') and explains the exact source ('the same list shown in the site's own header search box'). It does not name any sibling tool, so it falls short of the top score for distinguishing among alternatives, but its purpose is unambiguous.

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?

Provides contextual clues about what the tool returns and where the data comes from ('the same list shown in the site's own header search box before the visitor types anything'), which implies when to use it. However, it offers no explicit guidance on when to prefer it over siblings like fanaticscollect_search, nor any exclusions.

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