Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

psastore_product_recommendations

Retrieve related or complementary product recommendations for a PSA Store product handle, with configurable limit up to 20.

Instructions

List PSA Store product recommendations. Returns normalized recommended products for one PSA Team Store (https://store.psacard.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. Addedv1.17.5

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the burden and adds useful behavioral context: handle is resolved to a Shopify ID, the storefront URL is fixed server-side, and results are normalized. These details go beyond the schema and inform the agent of internal processing.

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?

Three concise sentences with no fluff. The main purpose is front-loaded, and the key details are presented efficiently.

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

Completeness3/5

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

No output schema exists, and the description only says 'normalized recommended products' without specifying the return shape (array, object, pagination). It is adequate for understanding the function but leaves some ambiguity about the response format.

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 parameters are well-documented. The description adds minor value by explaining the handle is a route handle that gets resolved, and that the URL is fixed, but it does not expand on limit or intent beyond schema.

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 lists PSA Store product recommendations for a single product handle, distinguishing it from psastore_product (details) and psastore_collection_products (collection items). The mention of 'normalized' and handle resolution adds specificity.

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?

It implies usage for getting recommendations for one product, but does not explicitly mention alternatives or when not to use it. The scope is clear ('for one PSA Team Store product handle'), but no sibling comparison is provided.

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