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

ghl-mcp-server-v2

by zackscriven

ghl_product_collection_create

Creates a new product collection for a specific location, enabling organized product grouping and navigation in GoHighLevel.

Instructions

Create Product Collection Create a new Product Collection for a specific location Endpoint: POST /products/collections (Version header: v3; source: v3/products-v3.json) Requires a Sub-Account (location) token. OAuth scopes: products/collection.write

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": {
      "body": "<body>"
    },
    "name": "ghl_product_collection_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesRequest body (schema carried verbatim from the official OpenAPI spec).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / seo / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "description": {
      -        "description": "The description which would be displayed in preview purposes",
      -        "example": "Collections where all the best products are available",
      -        "type": "string"
      -      },
      -      "title": {
      -        "description": "The title which will be displayed as an SEO format",
      -        "example": "Best Sellers",
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "description": {
      +        "description": "The description which would be displayed in preview purposes",
      +        "example": "Collections where all the best products are available",
      +        "type": "string"
      +      },
      +      "title": {
      +        "description": "The title which will be displayed as an SEO format",
      +        "example": "Best Sellers",
      +        "type": "string"
      +      }
      +    },
      +    "title": "CollectionSEODto",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / title
      Added value: +"CreateProductCollectionsDto"
  2. 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 establish the write/non-idempotent/open-world profile, and the description adds meaningful operational context on top: the version header, the POST endpoint, and the required OAuth scope. It omits what happens on duplicate slug or what the response contains, which keeps it below a 5.

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?

Four short lines with the operation stated first and prerequisites after; no filler. The endpoint/source-file line is slightly noisy but gives a genuine traceability signal.

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 one-parameter mutation with no output schema, the description covers operation, scope, auth requirement and OAuth scope, which is close to what an agent needs before calling. It stops short of noting the returned collection identifier or slug-uniqueness failure mode.

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 coverage is 100% and the single nested body object documents altId, altType, name, slug, seo, image and collectionId with examples. The description's only added mapping is 'for a specific location', which implicitly ties to altId/altType; the baseline 3 applies when the schema does the heavy lifting.

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 plus scope ('Create a new Product Collection for a specific location') and even the underlying endpoint, so the agent knows exactly which resource is affected. It never names the sibling operations (ghl_product_collection_update/list/get) that compete for the same noun, so it falls short of full 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 gives prerequisites (sub-account/location token, products/collection.write scope) that tell the agent whether it is entitled to call the tool, but never states when to choose this over update, get, or list. Usage is implied by the verb 'create' rather than explained.

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