Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pristine_marketplace_search_suggest

Retrieve products, collections, and query suggestions from Pristine Marketplace predictive search by entering a query; optionally set limits and suggestion types.

Instructions

Get Pristine Marketplace search suggestions. Returns products, collections, and query suggestions from Pristine Marketplace's (https://www.pristinemarketplace.com) predictive search. The storefront URL is fixed server-side.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
limitNoMaximum results per type, defaults to 10 and supports up to 20
typesNoComma-separated suggestion types. Allowed values: product, collection, query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose a genuinely useful trait (the storefront URL is fixed server-side, so no store parameter is needed) and enumerates return types, but it never states the operation is read-only or addresses permissions/rate limits.

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?

Two sentences, tightly front-loaded with the core action followed by return-value detail, with zero filler. 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 simple read-style suggest tool with fully documented parameters and no output schema, the description covers purpose, return types, and the fixed-URL constraint. It is close to complete, missing only an explicit statement that it is a read-only operation.

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 schema already documents all three parameters. The description's mention of products, collections, and query suggestions loosely maps to the 'types' parameter but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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?

The description gives a specific verb ('Get') and resource (Pristine Marketplace search suggestions) and clarifies the output is predictive search returning products, collections, and query suggestions. This distinguishes it in spirit from the full pristine_marketplace_search sibling, but it never names or contrasts that sibling explicitly.

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?

Usage is only implied by 'predictive search' and 'suggestions' - an agent can infer this is for autocomplete/typeahead rather than a full product search, but there is no explicit when-to-use guidance and no exclusion pointing to pristine_marketplace_search.

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