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

ghl-mcp-server-v2

by zackscriven

ghl_product_create

Creates a new product in GoHighLevel with specified name, location, and product type, enabling catalog setup through the API.

Instructions

Create Product The "Create Product" API allows adding a new product to the system. Use this endpoint to create a product with the specified details. Ensure that the required information is provided in the request payload. Endpoint: POST /products/ (Version header: v3; source: v3/products-v3.json) Requires an Agency or Sub-Account token. OAuth scopes: products.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_create"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.1.0
    • changedInput schema / properties / body / properties / label / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "endDate": {
      -        "description": "Start date in YYYY-MM-DDTHH:mm:ssZ format",
      -        "example": "2024-06-30T05:43:39.000Z",
      -        "type": "string"
      -      },
      -      "startDate": {
      -        "description": "Start date in YYYY-MM-DDTHH:mm:ssZ format",
      -        "example": "2024-06-26T05:43:35.000Z",
      -        "type": "string"
      -      },
      -      "title": {
      -        "description": "The content for the product label.",
      -        "example": "Featured",
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "title"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "endDate": {
      +        "description": "Start date in YYYY-MM-DDTHH:mm:ssZ format",
      +        "example": "2024-06-30T05:43:39.000Z",
      +        "type": "string"
      +      },
      +      "startDate": {
      +        "description": "Start date in YYYY-MM-DDTHH:mm:ssZ format",
      +        "example": "2024-06-26T05:43:35.000Z",
      +        "type": "string"
      +      },
      +      "title": {
      +        "description": "The content for the product label.",
      +        "example": "Featured",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "title"
      +    ],
      +    "title": "ProductLabelDto",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / properties / medias / items / title
      Added value: +"ProductMediaDto"
    • changedInput schema / properties / body / properties / seo / allOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "description": {
      -        "description": "SEO description",
      -        "example": "This is the best product you can buy online with amazing features and great value",
      -        "type": "string"
      -      },
      -      "title": {
      -        "description": "SEO title",
      -        "example": "Best Product - Buy Now",
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "description": {
      +        "description": "SEO description",
      +        "example": "This is the best product you can buy online with amazing features and great value",
      +        "type": "string"
      +      },
      +      "title": {
      +        "description": "SEO title",
      +        "example": "Best Product - Buy Now",
      +        "type": "string"
      +      }
      +    },
      +    "title": "ProductSEODto",
      +    "type": "object"
      +  }
      +]
    • addedInput schema / properties / body / properties / variants / items / properties / options / items / title
      Added value: +"ProductVariantOptionDto"
    • addedInput schema / properties / body / properties / variants / items / title
      Added value: +"ProductVariantDto"
    • addedInput schema / properties / body / title
      Added value: +"CreateProductDto"
  2. First observedv2.0.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new operational context: the endpoint path, the v3 version header, the Agency/Sub-Account token requirement, and the products.write OAuth scope. It stops short of describing duplicate-handling or error behavior, hence 4 rather than 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The first sentence repeats the tool name and title almost verbatim ('Create Product' / 'The "Create Product" API allows adding a new product'), and the second paragraph is filler. The endpoint/auth/scope lines that follow are dense and front-loaded with real value, so the bloat is confined to the lead.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation on a heavily nested body schema with no output schema, the description supplies the transport and auth context an agent needs, but says nothing about what is returned (e.g., a new product id) or about cross-field constraints such as the taxes/isTaxesEnabled and label/isLabelEnabled coupling documented only inside the schema. Adequate but with clear gaps.

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 deeply nested CreateProductDto (name, locationId, productType required, plus seo, variants, medias, taxes, labels) is already documented inline. The description contributes nothing about individual fields beyond 'required information', so the baseline 3 applies.

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 pairs a specific verb (create) with a specific resource (a product at POST /products/), so the operation is unambiguous. It never distinguishes this tool from nearby siblings such as ghl_product_update, ghl_product_bulk_edit, or ghl_product_price_create, which is the only thing keeping it from a 5.

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?

'Use this endpoint to create a product with the specified details' restates the purpose rather than giving selection guidance. There is no when-not-to-use, no mention of the update/bulk-edit siblings, and the only procedural hint is the generic 'ensure that the required information is provided in the request payload'.

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