Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official

alt_sold_listings

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.

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. Credential-free public data from Alt's own search backend. See alt-categories for the accepted category/auction_house/grading_company values.

Input Schema

TableJSON 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?

With no annotations, the description carries the burden and does so well: it discloses the rolling recent time window, multi-source aggregation, credential-free public data, and that url/listing_id fields differ depending on the source auction house. It omits return shape and rate/pagination behavior, but the core behavioral profile is present.

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 action and scoped with specifics, but the framing clause about Alt's 'card-investment-marketplace positioning' is promotional filler that could be cut. Most sentences earn their place.

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 six-parameter search tool with no annotations and no output schema, it covers data source, scope, filter sourcing, and cross-tool references. Pagination defaults live in the schema, so the remaining gap is minor.

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 already 100%, so 3 is the baseline. The description adds genuine meaning beyond it: auction_house=Alt is interpreted as Alt's own sales, listing_id/listing_type are flagged as the link into alt-listing, and alt-categories is named as the source of accepted enum 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: searches Alt's global archive of completed card sales aggregated across source auction houses. It explicitly distinguishes itself from alt-search/alt-auctions as a separate index scoped to a recent window rather than live listings, so an agent can route without opening a 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 for live data, alt-listing for certificate numbers) and the condition selecting them. It also tells the agent when to pass auction_house=Alt and where to find accepted filter values (alt-categories).

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