Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goldin_listing

Retrieve full public details for a single Goldin auction lot using its slug. Get title, description, current bid, auction window, grading, images, and adjacent lot links.

Instructions

Get one Goldin lot's full public detail. One lot's full public detail: title, description, current bid/starting price, auction window and status, grading info, images, and prev/next lot pointers within the same auction. slug is the meta_slug from a goldin-search result (or the trailing path segment of the lot's own goldin.co/item/{slug} page URL).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe lot's meta_slug, from a goldin-search result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.3/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 behavioral burden. It discloses that this is a public read of one lot and lists the data categories returned, which is useful. It does not cover failure modes, invalid slugs, or data availability, but for a simple detail fetch this is adequate baseline transparency.

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?

The description is compact and front-loaded with the core action. The second sentence slightly repeats 'full public detail' but justifies itself by listing the payload fields and the slug derivation. Minor redundancy only.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 key return fields: pricing, auction window/status, grading, images, and previous/next lot pointers. Combined with complete slug guidance, this is enough for an agent to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single slug parameter is already documented in the schema, and the description adds meaning by defining it as meta_slug from a goldin-search result and giving an equivalent derivation from the lot's goldin.co/item/{slug} page URL. This removes any ambiguity about which identifier to pass.

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?

The description opens with a specific verb and resource: 'Get one Goldin lot's full public detail.' It then enumerates the returned content, which differentiates this single-lot detail tool from search, auction, and category siblings.

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?

The description clearly tells the caller where to obtain the required slug: from a goldin-search result or the lot's own page URL. It doesn't explicitly name alternatives or state when not to use the tool, but the singular 'one lot' plus slug sourcing provides clear context among Goldin siblings.

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