Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

jcrew_suggest

Fetch J.Crew or J.Crew Factory search-box suggestions for a partial query, returning suggested phrases with live result counts; choose the storefront via site.

Instructions

Get J.Crew or J.Crew Factory search-box suggestions. Returns the storefront's own search-box suggestions (typeahead) for a partial query -- a flat list of suggested search phrases, each with its own live total result count on the search index. Select the storefront with site (default jcrew). Not product data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteNoStorefront to search
queryYesPartial search query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / site / enum
      Added value: +[
+  "jcrew",
+  "factory"
+]
  2. Addedv1.16.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the return type (a flat list of suggested search phrases with live total result counts) and notes it is not product data. It also implies a read-only operation ('Get') and clarifies the site parameter's default. This provides solid behavioral context without over-specifying.

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?

The description is two sentences long, front-loaded with the purpose, and contains no unnecessary filler. It efficiently conveys the core behavior, return shape, and parameter default in a structured manner.

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?

Given only two simple parameters and no output schema, the description provides a clear picture of what the tool returns (flat list with counts) and what it does not (product data). It does not mention pagination or limits, but for a typeahead suggest tool, this is likely sufficient. The lack of an output schema is mitigated by the description's mention of the return shape.

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?

The schema already covers both parameters with descriptions ('Partial search query' and 'Storefront to search'), so the baseline is 3. The description adds the default value for site (jcrew) and reiterates the 'partial query' aspect, which adds marginal value beyond the schema but does not significantly deepen understanding of parameter usage.

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 clearly states the tool's purpose: 'Get J.Crew or J.Crew Factory search-box suggestions.' It specifies the resource (J.Crew/J.Crew Factory search box) and the verb (get). It also distinguishes itself from product data by explicitly stating 'Not product data,' which helps differentiate from siblings like jcrew_search or jcrew_product.

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 description mentions 'Select the storefront with site (default jcrew)' but does not explicitly name alternative tools or provide a when-to-use vs. when-not-to-use comparison. The 'Not product data' statement is a partial exclusion, but it does not direct the agent to a specific alternative like jcrew_search. More explicit guidance would improve clarity.

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