Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

alt_listing

Get one Alt listing's full public detail. One listing's full public detail -- title, description, price/bid state, grading info, and images -- normalized across Alt's own native listings and its aggregated external listings.

Instructions

Get one Alt listing's full public detail. One listing's full public detail -- title, description, price/bid state, grading info, and images -- normalized 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

TableJSON 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 behavioral burden. It usefully discloses normalization across native and external listings and warns that 'not every response field applies to every listing_type,' plus points to a markdown doc for field notes. It stops short of covering auth requirements, rate limits, or 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?

Purpose is front-loaded and the field list, sourcing, and caveat follow in a logical order. There is minor redundancy ('full public detail' stated twice), but overall it is tight and every sentence contributes.

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 listing the returned fields and flagging listing_type-dependent variability. For a two-param fetch tool this is nearly complete, with only return-shape specifics deferred to an external markdown reference.

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 coverage is 100%, so the schema already documents both params and their enum values. The description restates the provenance of id/listing_type, mostly duplicating what the schema descriptions already say, adding little semantic value beyond the baseline.

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 and resource ('Get one Alt listing's full public detail') and enumerates the returned content (title, description, price/bid state, grading, images). It implies its place in a search/fetch flow by naming alt-search, alt-auctions, and alt-sold-listings as the sources it complements, though it does not explicitly contrast itself with siblings like alt_asset.

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?

Clearly states where the required inputs come from ('id and listing_type come from a prior alt-search/alt-auctions result, or from an alt-sold-listings result's listing_id'), which tells the agent when this tool applies. No explicit when-not condition is given, but the dependency on a prior search shifts usage into clear context.

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