Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

gymshark_collections

List Gymshark collections with pagination, returning normalized collection data from the fixed Gymshark storefront.

Instructions

List Gymshark collections. Returns normalized collections from Gymshark (https://row.gymshark.com). The storefront URL is fixed server-side. Valid empty result pages return 200 with an empty collections array.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page, defaults to 1
limitNoMaximum collections, defaults to 50 and supports up to 250

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.6/5.0
Behavior4/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 discloses useful behavioral traits: collections are normalized, the storefront URL is fixed server-side, and valid empty result pages return a 200 with an empty array. This goes beyond a simple restatement and helps the agent interpret unusual responses, though it does not detail the collection object shape.

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 compact and front-loaded, leading with the primary purpose and then adding only high-value behavioral notes. Every sentence contributes useful information without redundancy.

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 simple list endpoint with two optional parameters, the description covers the core purpose, source, server-side URL behavior, and the empty-result edge case. Since no output schema exists, mentioning that results are returned as a collections array is helpful, though the exact fields of a 'normalized collection' are not specified.

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%, so the schema already documents page and limit semantics. The description adds no additional parameter-level meaning, so a baseline score of 3 is appropriate.

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 action ('List Gymshark collections') and the resource, with added context about normalization and the source storefront. It does not explicitly differentiate itself from sibling tools like gymshark_collection_products, but the verb and resource are specific enough that an agent can infer the tool's role.

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 choose this tool instead of related siblings such as gymshark_collection_products or gymshark_products. The description implies a listing use case but provides no explicit exclusions or alternative routing.

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