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

ghl-mcp-server-v2

by zackscriven

ghl_product_collection_get

Read-onlyIdempotent

Retrieves details for a specific product collection by collection ID and location ID, helping you inspect collection data through the GoHighLevel API.

Instructions

Get Details about individual product collection Endpoint: GET /products/collections/{collectionId} (Version header: v3; source: v3/products-v3.json) Requires a Sub-Account (location) token. OAuth scopes: products/collection.readonly

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": {
      "collectionId": "<collectionId>",
      "altId": "<altId>"
    },
    "name": "ghl_product_collection_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
altIdYesLocation Id
collectionIdYesCollection Id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds genuine context beyond that: it requires a Sub-Account (location) token and the products/collection.readonly OAuth scope, plus the API version and spec source, which helps an agent anticipate auth failures.

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?

Four short lines, front-loaded with the purpose, then endpoint/auth metadata. No filler; every line contributes operational detail an agent may need before the call.

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 two-parameter read tool with full schema coverage, complete annotations and no output schema, this covers purpose, endpoint, auth token type and scope. The only gap is that it doesn't describe the shape of the returned collection, which is not strictly required here.

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% (both collectionId and altId documented), so the schema carries the parameter burden. The description's endpoint template reinforces that collectionId is the path identifier, but it says nothing about altId being the location id, adding little beyond the schema.

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 Details about individual product collection'), and the word 'individual' signals a single-record fetch rather than the list variant. It does not name the sibling tools (ghl_product_collection_list/create/update/delete) explicitly, but the singular framing is enough to distinguish it.

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 only implied: the endpoint template and 'individual' suggest fetching one collection when you already have a collectionId. There is no explicit when-to-use/when-not guidance or pointer to ghl_product_collection_list for enumeration.

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