Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

firstdibs_product

Fetch 1stDibs product details from a product URL, returning name, brand, category, description, images, price, currency, and in-stock status for product research or cataloging.

Instructions

Get a 1stDibs product. Returns the details of one 1stDibs product, identified by its product url: name, brand, category, description, images, price with currency, and the in_stock flag. The price is in USD and is present only when 1stDibs shows one.

Input Schema

NameRequiredDescriptionDefault
urlYes1stDibs product URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden and does add real value: it discloses the exact returned fields and the notable condition that price is USD and only present when 1stDibs shows one. It omits auth/rate-limit/error behavior, but for a read-only single-item fetch the disclosure is solid.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the action, followed by the identifier and the returned fields, then a conditional caveat. No filler and every sentence earns its 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 one-parameter lookup with no output schema and no annotations, the description supplies the return shape and the price caveat, which is enough to call it correctly. The only real gap is the absence of routing guidance relative to the sibling firstdibs_search.

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% for the single 'url' parameter, so the schema already documents it. The description confirms the URL identifies the product but adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 ('Get a 1stDibs product') and clarifies the lookup is a single product identified by URL, which cleanly distinguishes it from firstdibs_search. The return payload is enumerated up front.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The requirement of a product URL implies this is a detail/fetch tool used after obtaining a URL, but the description never names firstdibs_search or states when to prefer this over it. Usage is only inferable, not stated.

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