Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

alt_sold_listings

Query Alt's completed sales archive across auction houses, filtering by card category, grading company, or auction source.

Instructions

Search Alt's completed sales archive. Searches Alt's global archive of completed card sales, aggregated across every source auction house its search carries -- the "market data" side of Alt's card-investment-marketplace positioning. This is a separate index from alt-search/alt-auctions, scoped to a rolling recent time window, not a filtered view of live listings. Pass auction_house=Alt to see only Alt's own completed sales. Each of Alt's own sales carries listing_id and listing_type -- pass both to alt-listing to get that item's certificate number -- and its url is the alt.xyz item page; a sale aggregated from another auction house carries that source site's own url instead. See alt-categories for the accepted category/auction_house/grading_company values.

Input Schema

NameRequiredDescriptionDefault
qNoFree-text search across item name, subject, brand, and variety. Omit or pass * to browse the most recent sales.
pageNo1-based page number, default 1
categoryNoComma-separated card category filter
per_pageNoResults per page, default 24, max 100
auction_houseNoComma-separated source auction house filter. Pass Alt to see only Alt's own completed auctions.
grading_companyNoComma-separated grading company filter

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?

No annotations, so the description carries the full burden, and it does substantial work: it discloses that the index is aggregated across source houses, scoped to a rolling time window, that own-sales carry listing_id/listing_type while aggregated sales carry a foreign url. It does not describe pagination behavior or return shape in depth, keeping it just short of 5.

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 purpose and densely informative, but the opening two sentences restate the same idea ('Search Alt's completed sales archive' / 'Searches Alt's global archive of completed card sales'), a minor redundancy in an otherwise tight block.

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?

With no output schema, the description compensates by describing what each sale record carries (listing_id, listing_type, url, source-dependent url) and the aggregation scope. It omits pagination limits and result-page structure, but is otherwise complete for a 6-param search tool.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains what auction_house=Alt does, that q browses recent rows when omitted, and that listing_id/listing_type chain to alt-listing. It also routes the agent to alt-categories for the enum values rather than restating them.

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 ... completed sales archive') and immediately disambiguates it from the sibling tools alt-search/alt-auctions and from live listings. An agent can distinguish the scope without opening any 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 names the alternatives (alt-search/alt-auctions) and how this differs ('separate index ... rolling recent time window, not a filtered view of live listings'), plus the auction_house=Alt condition for Alt-only results. Points to alt-categories for enum values and alt-listing for follow-up certificate lookup.

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