Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

goat_product_recommended

Find recommended and related products for a GOAT product page by slug, returning other colorways and similar items with descriptive metadata only.

Instructions

Get GOAT recommended products for a product. Returns the recommended/related products GOAT's own product page shows for a given product (other colorways, similar products) -- descriptive metadata only, no live pricing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesGOAT product URL slug to find related products for
countNoNumber of recommended products to return, defaults to 8, maximum 24

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

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 full behavioral burden and does disclose two useful traits: the data source is GOAT's own product page and it is 'descriptive metadata only, no live pricing.' That pricing/temporal caveat is genuinely valuable. It stops short of covering rate limits, auth, or pagination.

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 tight sentences, purpose front-loaded, no filler. The clarifying clause about colorways/similar products and the no-pricing caveat both earn their 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 2-param read tool with no annotations and no output schema, the description covers purpose, scope, and the key limitation well. Minor gaps remain around return count behavior and pagination, but nothing essential is missing for correct invocation.

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% (slug and count are both documented in the schema, including the default 8 / max 24 on count). The description adds nothing about parameter format or meaning beyond what the schema already states, so the 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?

States a concrete verb+resource ('Get GOAT recommended products for a product') and the second sentence sharpens what 'recommended' means here (other colorways, similar products), which separates it from the plain goat_product lookup. It does not name the sibling it complements, so it falls short of an explicit sibling differentiation.

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 implies the use case (supply a product slug, get related products) but never states when to call this instead of goat_product, goat_search, or goat_curated, and gives no exclusions or prerequisites. Usage is only inferable.

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