Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ohpolly_product_recommendations

Fetch normalized product recommendations for an Oh Polly product handle by resolving it to a Shopify ID, supporting related or complementary intent.

Instructions

List Oh Polly product recommendations. Returns normalized recommended products for one Oh Polly (https://www.ohpolly.com) product handle. The route handle is resolved to a Shopify product id before fetching recommendations. The storefront URL is fixed server-side.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum products, defaults to 10 and supports up to 20
handleYesProduct handle
intentNoRecommendation intent. Allowed values: related, complementary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / intent / enum
      Added value: +[
+  "related",
+  "complementary"
+]
  2. Addedv1.16.0

TDQS

A4/5.0
Behavior3/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 usefully discloses that the handle is resolved server-side to a Shopify product ID and that the storefront URL is fixed, but it does not describe output shape, pagination, errors, or potential side effects. For a simple listed read tool this is adequate but not rich.

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 three sentences with no filler: it front-loads the core action, adds the single-input constraint, and closes with a relevant server-side detail. Every sentence contributes information.

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 three-parameter read tool it covers the essential call pattern: one handle, optional limit/intent (documented in schema), normalization, and fixed storefront URL. The absence of an output schema makes the vague phrase 'normalized recommended products' a small gap, but it's enough for a correct first call.

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 covers all three parameters at 100%, so the baseline is 3. The description adds a small amount of context by explaining that the handle resolves to a Shopify ID and that products are normalized, but does not materially expand on limit or intent beyond their schema descriptions.

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 the specific verb 'List' and the resource 'Oh Polly product recommendations,' then narrows it to 'one ... product handle.' It distinguishes from sibling tools like ohpolly_product and ohpolly_products by focusing on recommendations for a single handle.

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?

It states the required context: recommendations are fetched for a single product handle, and explains that the handle is resolved to a Shopify product ID. However, it does not explicitly name alternative tools or state when not to use this one, such as when fetching product details instead of recommendations.

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