Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

alt_search

Search live auction and fixed-price card listings across Alt's aggregated marketplace by keyword, category, grader, source, and sort order.

Instructions

Search Alt's aggregated card marketplace. Searches Alt's universal aggregator index -- live auction and fixed-price listings from Alt itself and every other source auction house its search carries (eBay, Fanatics Collect, Pristine Auction, Goldin, CardHobby, Memory Lane) -- by free-text query, category, source auction house, grading company, and listing type, in a caller-selected sort order. Only currently-live listings are returned; see alt-sold-listings for completed sales. See alt-categories for the accepted category/auction_house/grading_company/listing_type/sort values.

Input Schema

NameRequiredDescriptionDefault
qNoFree-text search across item name, subject, brand, and variety. Omit or pass * to browse everything.
pageNo1-based page number, default 1
sortNoResult order. Default recommended.
categoryNoComma-separated card category filter
per_pageNoResults per page, default 24, max 100
listing_typeNoComma-separated listing type filter. Omit to search auctions and fixed-price listings from every source together.
auction_houseNoComma-separated source auction house filter
grading_companyNoComma-separated grading company filter

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/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 full burden; it usefully discloses that only currently-live listings are returned and enumerates the aggregated sources. It omits auth, rate-limit, pagination, and response-shape context, but the key behavioral constraint is clearly stated.

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-loads the core purpose and stays to a tight paragraph; the parenthetical source list and cross-references earn their place. Slightly dense but no filler.

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 complex 8-param aggregator search with a fully documented schema and no output schema, the description is nearly complete: purpose, sources, live-only scope, and where to find values are all present. Return format is implicitly listings and not spelled out, which is a minor gap.

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%, so the schema already documents all 8 parameters and their enums; baseline 3 applies. The description adds only a pointer to alt-categories for accepted values, which is marginal since the schema already inlines the enums.

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+resource ('Search Alt's aggregated card marketplace') and precisely scopes it as a universal aggregator index across named sources. It distinguishes itself from the sibling alt_sold_listings and names the facets it searches, so an agent can tell what it does 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes to alternatives: alt-sold-listings for completed sales and alt-categories for accepted enum values, and states the live-only scope. It does not address the overlapping sibling alt_card_search, so coverage is clear but not exhaustive.

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