Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

goat_collection

Fetch a paginated GOAT curated product collection by slug, such as trending or new arrivals, to populate product rails and recommendation modules.

Instructions

Get a GOAT curated product collection. Returns a page of one of GOAT's curated product collections (an editorial rail like "top trending" or "new arrivals"), as shown in GOAT's own product-page "you may also like" rails and homepage modules. Collection slugs are not enumerable by this API -- capture one from a live GOAT page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "goat_collection"
  }
}

Input Schema

Name	Required	Description
`page`	No	1-indexed result page, defaults to 1
`slug`	Yes	GOAT collection slug, e.g. as seen in a curated rail on GOAT's own site
`limit`	No	Results per page, defaults to 12, maximum 100
`exclude_product_ids`	No	Omit specific products by id, comma-separated

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.16.2Sep 10, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden. It discloses the paginated nature of the result ('returns a page of...') and the non-enumerable slug constraint, which is valuable. It says nothing about authentication requirements, rate limits, or what a bad slug returns, so the behavioral picture is only partially filled in.

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 sentences, front-loaded with the core action and return shape, followed by the critical slug-acquisition caveat. Every sentence contributes; only the repeated mention of GOAT's own rails is slightly redundant.

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 4-parameter read tool with no annotations and no output schema, the description covers what the tool returns (a page of a curated collection) and the single hardest operational issue (where to get a slug). Auth, error behavior, and sibling differentiation remain unaddressed, which keeps it short of fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the baseline is 3. The description goes beyond the schema by explaining that the slug namespace is not discoverable through this API and must be harvested from a live GOAT page, which is operationally meaningful context the schema's example-only hint does not convey.

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 specific verb and resource: 'Get a GOAT curated product collection', and clarifies it is an editorial rail like 'top trending' or 'new arrivals' rather than a generic product list. It does not, however, explicitly distinguish itself from the similarly named sibling goat_curated, leaving the agent to guess which collection endpoint to pick.

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 gives one genuinely useful usage constraint: slugs are not enumerable and must be captured from a live GOAT page, which tells the agent not to expect a discovery path here. Beyond that, there is no guidance on when to prefer this over goat_curated, goat_search, or goat_product_recommended, so the when-to-use decision is left implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server