Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

skims_product_recommendations

Fetch SKIMS product recommendations by product handle, returning normalized related or complementary products with an optional limit.

Instructions

List SKIMS product recommendations. Returns normalized recommended products for one SKIMS (https://skims.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

B3.1/5.0
Behavior3/5

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

The description discloses some internal behavior (handle resolved to Shopify ID, fixed server-side URL) but doesn't cover edge cases like invalid handles, error behavior, or the exact output format. Since there are no annotations, the description carries the full burden, and while it adds context, it's incomplete.

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

Conciseness4/5

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

The description is concise, with the main purpose stated first, followed by relevant technical details. It's not overly verbose, though the technical details could be considered optional. It's well-structured for quick comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description should provide more details about the return value. It only vaguely says 'normalized recommended products' without specifying structure or potential errors. For a tool with three parameters, this is insufficient for an agent to fully understand the response and handle failures.

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 coverage is 100%, so each parameter already has a description. The description adds a minor detail about handle resolution but doesn't elaborate on limit or intent beyond what the schema states. It doesn't significantly enhance parameter understanding.

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 clearly states the tool lists SKIMS product recommendations and takes a product handle, which differentiates it from sibling tools like skims_product or skims_products that likely return product details. However, it doesn't explicitly contrast with these siblings, so it's clear but not maximally differentiated.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives. The description doesn't mention that it's specifically for recommendations rather than product info, nor does it mention any exclusions or alternative tools. An agent would need to infer its use from the name and context.

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