Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fanaticscollect_listing

Retrieves full details for a single Fanatics Collect listing, including auction or buy-now pricing, bids, status, images, sale history, and vault grading/PSA verification.

Instructions

Get Fanatics Collect listing detail. Returns full detail for a single Fanatics Collect listing: a weekly-auction lot, a premier-auction lot, or a fixed-price "buy now" item (including an Instant Rips pack). Fields include title, current bid/starting/asking price, bid count, auction window and status, images, description, completed sale history, and -- when the card is stored in Fanatics' vault -- grading/authentication metadata including a direct PSA cert-verification link. Costs 1 credit per successful call.

Input Schema

NameRequiredDescriptionDefault
idYesListing UUID
typeNoListing type. Default: WEEKLY

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses a cost of 1 credit per successful call, enumerates returned fields, and notes vault-specific grading/authentication metadata including a PSA cert-verification link; it still omits auth requirements, rate limits, and error behavior.

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, front-loaded with the purpose and then useful type/field details plus the credit cost. It is dense but every part is relevant to calling the tool correctly.

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 single-record detail endpoint with no output schema, the description provides a solid field inventory, listing-type coverage, and cost. It leaves minor gaps around routing to search/sold-items siblings and operational details like authentication or error behavior.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds meaning to the type enum by mapping WEEKLY/PREMIER/FIXED to weekly-auction lots, premier-auction lots, and fixed-price 'buy now' items including Instant Rips packs; it does not expand on id beyond the schema's 'Listing UUID' description.

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 ('Get') and resource ('Fanatics Collect listing detail'), and clarifies that it returns detail for a single listing among weekly-auction, premier-auction, and fixed-price types. It is clear, though it does not explicitly name sibling tools such as fanaticscollect_search for finding listing IDs.

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?

The description implies usage when full detail for a single listing is needed and lists the listing types it covers. However, it gives no explicit when-to-use versus alternatives like fanaticscollect_search or fanaticscollect_sold_items, nor guidance on where to obtain the required listing UUID.

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