Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanaticscollect_auctions

Find Fanatics Collect's current and recent auction events, then use an event URN to browse every lot in that sale.

Instructions

List Fanatics Collect auction events. Returns Fanatics Collect's current and recent weekly and premier auction events -- the same short list the site's own header auction switcher and countdown banner show. This is the discovery endpoint for Search's auction_urn param: copy an event's urn value to browse every lot in that auction. A small, current/recent set (observed live: around 6 events), not a full historical archive -- older auctions' urn values found on a Search result or a GetListing response remain valid for Search even once they no longer appear here.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.5/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 and does well: it discloses the result set is small (observed live around 6 events), limited to current/recent auctions, and explicitly not a historical archive. It adds the non-obvious durability fact that older urn values stay valid for Search after dropping off this list. It does not address auth or rate limits, but for a param-less read endpoint the disclosure is strong.

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 the core verb+resource, followed by return scope, integration purpose, and the archive caveat. Every sentence earns its place, though the parenthetical and appended clause about older urn values make the tail slightly dense for a single-sentence list tool.

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 zero-param, no-output-schema endpoint, the description covers what comes back, how big it is, its recency window, and how to consume the urn values. Nothing critical is missing, though it stops short of noting any auth or freshness/refresh cadence.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so per the baseline this scores 4. The schema is empty and the description correctly does not invent parameter semantics, instead explaining the downstream use of the return values.

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 ('List Fanatics Collect auction events') and immediately scopes it to current and recent weekly/premier events, tying it to a recognizable surface (the site's header switcher and countdown banner). An agent can distinguish it from fanaticscollect_search or fanaticscollect_listing without opening the 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?

Explicitly identifies itself as the discovery endpoint for Search's auction_urn param and tells the agent to copy an event's urn to browse every lot. It also names the alternatives (Search results, GetListing responses) that supply urn values when this list doesn't show them, so when-to-use and when-not-to-use are both covered.

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