Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

firstdibs_designers

Lists 1stDibs designer filter values with names, slugs, and URLs for an optional category, enabling you to select a slug for use in 1stDibs search.

Instructions

List 1stDibs designers. Lists the designer filter values found on a 1stDibs category page, with a count and, for each designer, its name, slug and url. category is optional and comes from firstdibs-categories. Each slug can be used as the designer filter in firstdibs-search.

Input Schema

NameRequiredDescriptionDefault
categoryNoCategory slug from firstdibs-categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/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. It usefully discloses the return shape (`count`, `name`, `slug`, `url`), which matters given there is no output schema, and 'List' implies a non-destructive read. However, it omits pagination behavior, auth requirements, and rate limits for a network-backed listing tool.

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?

Four tight sentences with zero waste: purpose first, then output shape, then the optional input, then downstream usage. Every sentence earns its place and nothing is front-loaded poorly.

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?

For a single-parameter, non-annotated list tool with no output schema, the description fully covers what the tool returns, where its input comes from, and how its output feeds firstdibs-search. An agent has everything needed to call it correctly.

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 single `category` parameter is already documented in the schema. The description adds only that it is optional and comes from firstdibs-categories, which largely restates the schema's own description. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('List 1stDibs designers') and precisely scopes it as 'designer filter values found on a 1stDibs category page'. It names the sibling tools it relates to (firstdibs-categories, firstdibs-search), so an agent can distinguish it from those without opening schemas.

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?

Explains that `category` is optional and originates from firstdibs-categories, and that each returned `slug` feeds the designer filter in firstdibs-search. This gives clear chaining context and the input's provenance, though it doesn't explicitly state when NOT to use it or contrast with a hypothetical sibling designer-listing alternative.

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