Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

alt_listing

Fetch full public details for one Alt listing by ID and type, including title, description, price or bid state, grading info, and images across native and external sources.

Instructions

Get one Alt listing's full public detail. One listing's full public detail -- title, description, price/bid state, grading info, and images -- across Alt's own native listings and its aggregated external listings. id and listing_type come from a prior alt-search/alt-auctions result, or from an alt-sold-listings result's listing_id and listing_type for a completed sale on Alt itself. Not every response field applies to every listing_type -- see the field-level notes in this endpoint's markdown doc.

Input Schema

NameRequiredDescriptionDefault
idYesThe listing's id, from a Search/Auctions result's id field, or a sold-listings result's listing_id for a completed sale on Alt itself
listing_typeYesThe listing's listing_type from the same Search/Auctions result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.12
    • changedInput schema / properties / id / description
      Previous value: -"The listing's id, from a Search/Auctions result's id field"New value: +"The listing's id, from a Search/Auctions result's id field, or a sold-listings result's listing_id for a completed sale on Alt itself"
  2. Addedv1.17.5

TDQS

A3.6/5.0
Behavior3/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. 'Get ... full public detail' implies a safe read, and it usefully discloses that not every response field applies to every listing_type and points to a markdown doc for field-level notes. However, it says nothing about auth requirements, rate limits, or the non-mutating guarantee explicitly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening two sentences restate the same idea ('Get one Alt listing's full public detail' then 'One listing's full public detail -- ...'), which is wasted space. The provenance guidance that follows is valuable, but the redundant lead-in costs conciseness.

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 shoulders the return-value burden and does list the key fields (title, description, price/bid state, grading info, images) while flagging that fields vary by listing_type. It defers the authoritative field notes to an external markdown doc, which is a minor gap given the absence of an output schema.

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 both parameters are already documented in the schema (including the enum for listing_type). The description's added value is limited to restating the provenance of id/listing_type and the caveat that response fields vary by listing_type, so the baseline of 3 is warranted.

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 (one Alt listing's full public detail) and enumerates the returned content (title, description, price/bid state, grading info, images). It distinguishes scope by noting coverage of native and aggregated external listings, though it doesn't explicitly name a sibling it is not (e.g. alt_search), leaving differentiation largely implied.

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?

Gives clear prerequisite context: id and listing_type must come from a prior alt-search/alt-auctions result, or from a sold-listings result's listing_id for an Alt completed sale. This tells the agent when the tool is applicable and how to source inputs, but stops short of stating exclusions or an explicit alternative to prefer in other cases.

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