Skip to main content
Glama
ghl-mcp-server-v2

ghl-mcp-server-v2

by zackscriven

ghl_product_collection_list

Read-onlyIdempotent

Fetch product collections for a location, search by collection name or IDs, and paginate results to retrieve complete lists.

Instructions

Fetch Product Collections Internal API to fetch the Product Collections Endpoint: GET /products/collections (Version header: v3; source: v3/products-v3.json) Requires a Sub-Account (location) token. OAuth scopes: products/collection.readonly Pagination params: limit, offset — pass them to page through full result sets.

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": {
      "altId": "<altId>",
      "altType": "<altType>"
    },
    "name": "ghl_product_collection_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoQuery to search collection based on names
altIdYesLocation Id
limitNoThe maximum number of items to be included in a single page of results
offsetNoThe starting index of the page, indicating the position from which the results should be retrieved.
altTypeYesThe type of alt. For now it is only LOCATION
collectionIdsNoIds of the collections separated by comma(,) for search purposes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description still adds genuinely useful context beyond that: the required location-token auth model, the exact OAuth scope (products/collection.readonly), and pagination behavior.

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?

Front-loaded with the action and endpoint, then auth, scope and pagination in short lines. The only waste is the near-duplicate opening pair ('Fetch Product Collections' / 'Internal API to fetch the Product Collections'), which restates the title verbatim.

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 read-only paged list with full schema documentation and complete annotations, the description covers endpoint, auth, scope and paging. The only gap is that with no output schema it does not characterize the returned collection objects or total-count behavior.

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 all six parameters are already documented in the schema, making 3 the baseline. The description only reinforces the limit/offset paging semantics and says nothing extra about the name or collectionIds filters, which are the parameters most likely to confuse an agent.

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 ('Fetch Product Collections') and the underlying endpoint GET /products/collections. It is clearly distinct from sibling mutations like ghl_product_collection_create/update/delete, but it never explicitly contrasts itself with ghl_product_collection_get (single-collection retrieval) or ghl_product_list.

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?

Usage is implied rather than stated: it notes a Sub-Account (location) token is required and that limit/offset should be passed to page through full result sets. There is no explicit 'use this when you need to enumerate collections vs. get one by id' routing guidance against the sibling read tools.

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